Troubleshooting
Notifications or reports are failing
Distinguish configuration, generation, delivery, destination, permission, and browser-download failures.
Last reviewed September 12, 2026
Notifications are not delivered
If notifications are not delivered, confirm that the alert policy is enabled, its issue or anomaly condition met the count threshold, the destination and recipient are valid, and SiteWall recorded an attempt. Then check the receiving service’s permissions, endpoint state, filtering, and history.
Diagnostic procedure
- 1.
Open the correct project and page
Use the project selector to choose the affected website, then open Alerts 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.
Policy evaluation
Read the configured value at Global, Provider, and Resource layers and identify the resolved effective state. Apply the narrowest approved change, validate critical journeys, and retain the previous state for recovery.
- 4.
Configuration
Record the current value, change only the setting required for the task, save it once, and verify the resulting state.
- 5.
Status
Read the state together with its timestamps and owner action; a workflow state does not erase the original observation.
- 6.
Destination checks
Trace the relationship from the loading resource to the observed destination or capability. Confirm required service endpoints and regional behavior in representative journeys before restricting access.
- 7.
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.
- 8.
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.
A compliance report does not generate or download
If a compliance report does not generate or download, confirm the active project, access, available framework records, and browser download permissions. Distinguish a still-generating state from a failed generation, preserve the timestamp and visible error, retry once, and escalate with project and report context.
Diagnostic procedure
- 1.
Open the correct project and page
Use the project selector to choose the website you intend to review, then open Legal & Compliance in the left navigation. Confirm the organization, project, and monitored domain before interpreting a record or changing a control.
- 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.
Access
Follow the indicator to its source records and preserve the project, monitored pages, observation period, generation time, reviewer, and known gaps. Keep SiteWall’s browser-side evidence separate from organizational evidence and the reviewer’s compliance conclusion.
- 4.
Generation state
Read the workflow state with its timestamps, affected entity, and owner action. Acknowledging or closing a record changes review status; it does not remove the underlying observation or prove remediation.
- 5.
Browser download checks
Compare observed browser access with the resource’s documented business purpose and the journeys that depend on it. Observed use can inform a least-privilege baseline, but unobserved use may still occur in untested states.
- 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.