Troubleshoot without losing context

1. Confirm the correct WordPress site and current filters in Activity. Reset the filters if necessary.
2. Check Collection controls for excluded categories and Privacy and retention for the relevant evidence period.
3. Open System status and read the collection, retention and background-work state. Preserve the exact failure code and when it occurred.
4. For request visibility, use Requests → Source and verification and the Observer self-test. Remember that cached and upstream traffic may be outside the observer.

Inspect the specific export, report or alert history. Pending, cancelled, suppressed, failed and accepted are different results. A returned background tick does not prove all work completed, and WordPress scheduling depends on the host's cron setup.

For advanced alerts, check both saved rule state and destination state. For private background exports, resolve the storage requirement shown by the interface. Do not change filesystem permissions to make private files publicly accessible.

Under Diagnostic export preview, inspect the complete snapshot before confirming Download diagnostic JSON. The preview describes versions, scoped counts, configuration flags and sanitized state codes; it excludes audit records, credentials, recipient addresses, destination URLs and private paths.

The preview expires after five minutes. Reload for a fresh preview if needed. Keep raw activity, webhook URLs, encryption keys and customer information out of ordinary support messages.