Configuration issues and performance basics
Updated 19/11/2026
Slow or incorrect behavior may come from repeated data access, an unsuitable refresh policy or unexpected rule selection. Reproduce the problem with measurable evidence before choosing a fix. Performance changes must preserve correctness.
Use focused tests to validate rules and broader tests to validate journeys. Compare expected and actual data before changing configuration. Tracer and Clipboard help investigate rule execution and runtime values where supported. Use diagnostic tools in controlled environments and avoid exposing personal data. Deployment requires functional, integration, security and regression checks.
Compare one intake journey with expected versus repeated service calls. Propose a cache change and identify how to test that applicant data stays isolated and current.
Return to curriculum