Troubleshoot without losing context
Start with the symptom, check the relevant state, and gather a small support record without exposing private evidence.
For Free 1.2.7 and Pro 1.2.7. Check the download page for available versions and requirements. Verify representative workflows on staging before use.
On this page
Logged.ai → Settings → System status
Check the specific record, job or destination before retrying. “Pending,” “accepted” and “complete” describe different stages.
| What you notice | Check first | Next step |
|---|---|---|
| A change is missing from Activity | Correct site, active filters, optional collection categories and retention. | Reset filters, then inspect Settings → System status. See coverage limits. |
| A request is missing | Requests → Source and verification, then the Observer self-test. | Check whether the request reached WordPress. Cached or upstream traffic may be outside this observer. |
| A button or page is unavailable | Account, site/network context, permissions and active package pair. | Use the scope and permission checks before changing access. |
| A form says it is stale | Whether another administrator or tab changed the saved configuration. | Reload the current values, review your intended change and save again. |
| The live demo will not save or export | The demo banner and allowed actions. | This is intentional. Use a separate staging installation to test writes or downloads. |
Note the exact message, time and timezone before changing settings. If you can reproduce the issue safely, use a fictional test record on staging rather than editing customer data.
A content or evidence link is missing
Check the selected site, current item/evidence permissions and retention. Deleted content and removed or expired evidence cannot be reopened. A current content title is only navigation context; it cannot restore a missing historical value. A synthetic alert test has no real triggering evidence. For Save this Activity view, remove unsupported free text and use a Recorded action filter. None of these checks requires broadening someone’s access.
Collection paused or report records unavailable
Read System status before trying to recreate data. Unreadable privacy settings require a deliberate valid settings save; busy privacy coordination can be retried. Inconsistent report metadata can leave an owner-visible job available for cancellation while output is refused. Neither repair recreates evidence that expired, was erased or was never collected.
Why one failed sign-in can leave no Activity row
Failed sign-ins are grouped: ten observed failures in the same fixed five-minute interval create a burst entry. Fewer failures have no individual Activity entries. Intervals restart every five minutes, so attempts on different sides of a boundary count separately. Supported WordPress failures against an existing account can also create a separate account-targeted burst. This identifies the account targeted, not the person attempting to sign in; passwords and attempted login text are not retained.
Requests contains matching findings, not a complete sign-in or traffic log. An upstream block or unsupported authentication integration may never reach the supported WordPress hooks. If an expected burst is missing, inspect System status and collection coverage.
| State or symptom | What it tells you | Useful action |
|---|---|---|
| Pending / queued | Work has been admitted, not necessarily completed. | Inspect that export, report or alert’s history and the host’s WordPress cron setup. |
| Suppressed / cancelled | A rule, permission or current configuration prevented this attempt. | Read the recorded reason. Do not assume that repeating the same request will deliver it. |
| Accepted by transport | The mail subsystem or destination transport accepted the attempt. | Check the recipient mailbox or receiving application and its delivery logs; acceptance does not prove receipt. |
| Delivery unknown | The outcome of an interrupted attempt could not be confirmed. | Check delivery history and the receiving system before attempting a manual resend. |
| Background export unavailable | Its private-storage or encryption requirements may be missing. | Read the interface’s prerequisite message. For a small activity selection, consider Download now instead. |
| Schema upgrade pending | Work needing the new schema may be paused. | Open Schema upgrade and follow the saved phase. |
For advanced alerts, inspect both the saved rule and its destination state. A successful background tick does not prove that every queued job completed. New saved exports use encrypted database chunks and require PHP Sodium, the original WordPress authentication salts and working scheduling. If an older job still uses private files, preserve its original storage and owner-only permissions for reads and cleanup; do not make a legacy export directory public to bypass an error.
- Open Settings → System status and copy the exact finite error/state code, plus the time it occurred.
- Under Diagnostic export preview, inspect the complete JSON before choosing Download diagnostic JSON.
- The preview expires after five minutes. Reload for a fresh preview if it expires or your access changes.
- Send the symptom, shortest safe reproduction, expected result, actual result and versions. Include the reviewed diagnostic file only when useful.
What the diagnostic JSON includes
Versions, scoped queue counts, configuration flags, sanitized state codes and permitted table-size estimates. It excludes audit records, account identifiers, email addresses, destination URLs, credentials and private paths. A diagnostic download is not an evidence export.
Do not paste licence keys, webhook URLs, encryption keys, raw activity or customer details into an ordinary support message. Use Support for the appropriate contact route.
This guide covers Logged.ai Free 1.2.7 and Pro 1.2.7. Check available versions and package requirements, and verify representative workflows on staging before updating your main site.
Get help with your next step.