Troubleshooting
A finding appears incorrect
Verify entity identity, observation time, rule configuration, supporting context, and expected behavior.
Last reviewed September 12, 2026
If a finding appears incorrect, verify project and entity identity, observation time, rule configuration, resource version, linked session, technical and raw context, and expected website behavior. Acknowledge it while reviewing; close it only after recording the validated disposition or baseline decision.
Diagnostic procedure
- 1.
Open the correct project and page
Use the project selector to choose the affected website, then open Issues in the left navigation. Reproduce the symptom in the same project, page, and observation window captured before you began.
- 2.
Preserve the failing state
Capture the exact symptom, affected URL, browser, time, record link, active filters, effective policy, and most recent deployment or configuration change. Avoid refreshing away evidence you may need.
- 3.
Context review
Compare the signal with the affected entity, representative session, expected behavior, recent deployments, and configured detection settings. Record the reason for the disposition before tuning detection or policy.
- 4.
Rule configuration
Record the current value, change only the setting required for the task, save it once, and verify the resulting state.
- 5.
Escalation evidence
Preserve source, time, project, and transformation context and separate the technical record from the reviewer’s conclusion.
- 6.
Retest after one reversible change
Reproduce the same page and journey after each check. Compare the new record with the preserved failing state, and stop when the evidence points to a different component or owner.
- 7.
Prepare an escalation packet if unresolved
Include the project, URL, time range, browser, record links, current and expected states, checks completed, changes reverted, and the team that owns the next dependency.