| API requests fail | Inspect the HTTP status and error code; check the healthcheck and service status. | For 401, correct the credential or environment. For 403, check scope and entitlement. For 429, respect Retry-After. |
| A connection needs attention | Check consent, provider permissions, reauthorization status, and the last successful synchronization. | Reauthorize through the supported flow when required; do not repeatedly reconnect to bypass provider limits. |
| Data appears old | Compare source observation time, last synchronization, and the provider’s supported refresh behavior. | Review data refresh and identify the affected resource. |
| Insights has not completed | Read the job or workflow state, missing inputs, and required actions. | Distinguish queued work, partial evidence, and failed processing before retrying. |
| Signal has no new alert | Check enrolled monitoring scope, cadence, consent, data freshness, and configured rules. | No alert alone does not prove a refresh occurred or that risk is unchanged. |
| A webhook is missing | Check destination availability, signature verification, deduplication, and delivery references. | Follow webhook guidance and reconcile through authorized resource reads. |
| A report does not reconcile | Compare the same billing account, time basis, date window, and snapshot; include reversals and pending activity correctly. | Use consumption reporting and send the statement references. |
| Credits do not reflect a payment | Check the credit report snapshot and whether the amount is pending or posted. | Send the payment reference to support or your account manager for reconciliation. There is no customer top-up or payment-method endpoint. |
