Read the last event
Check the account, environment and last successful sync. The fixed snapshot has three active connections out of five. Acme Robotics has a production-events connection and a Slack connection requiring attention after authorization failures.
Repair the cause first
A 401 or 403 requires a credential or permission review; repeated retries will not repair authorization. For 429, respect Retry-After. For a transient 5xx or timeout, retry only after checking whether the prior operation already completed.
Confirm recovery from a new event
An accepted retry means the request was accepted, not that all data is synchronized. Inspect the resulting event and connection state. Keep the original incident linked until you can verify the expected records or delivery; do not infer recovery from a disappearing spinner.