Open Logs to inspect site communication in the current organisation. Filter by site, module, operation, request outcome, processing state, time range, or text. Search can match a summary, error code, or correlation ID. Each urgent phone alert sent appears as a row with the operation phone_alert, for example "Urgent alert by SMS: delivered". It is recorded as sent by the system. The phone number is not shown. Choose phone_alert under Operation to see only these. The Connector's Test connection (or drush sentinel_connector:check) appears as a row with the operation connection_check; it stores no inventory and does not count against the plan's push limit. Choose connection_check to see only these. Clear filters to widen the result, select Refresh for current data, and use Load more for older entries.
Open an entry for its details. Review the request time, HTTP result, processing result, identifiers, and error information shown. Logs show safe summaries rather than secret credentials.
Request outcome and later processing are separate:
- Accepted, queued or Accepted, processing: work is not finished.
- Completed: the recorded operation completed.
- Superseded by a later sync: later inventory replaced this queued work.
- Accepted, processing failed or expired: receipt succeeded but later work did not.
- Rejected, Rate limited, or Service unavailable: follow the stated reason before retrying.
Use the site, time, and correlation ID when asking for support. Do not send API keys or passwords. Communication Logs record site requests. Use Audit log for account and administration actions.