Delivery retries and troubleshooting
UserGist durably queues destination deliveries after accepting a catalog event. Provider outages do not fail UserGist ingestion or API readiness.
Status meanings
| Dashboard status | Meaning |
|---|---|
| Accepted by provider | The provider ingestion API accepted the event. UI visibility may take a short delay. |
| Retrying | A temporary network, timeout, rate-limit, or provider error will be retried. |
| Failed | A permanent validation error or retry limit moved the delivery to dead letter. |
| Skipped | Delivery was dropped because its category was disabled, or the destination was paused/disconnected. |
Retries use exponential backoff and provider event IDs for deduplication. An event is dead-lettered after ten attempts or 24 hours. Authentication failures put the destination into Needs attention and stop repeated credential calls until a valid credential is connected.
Pause and resume
Pause immediately marks pending deliveries skipped and drops new events while paused. Those events are not buffered or replayed after resume. Disabling a category has the same prospective behavior for that category.
Disconnect
Disconnect wipes the credential and skips queued deliveries without deleting audit history. Events already accepted by the provider remain there.
Test connection
Use Test connection to send a fresh UserGist Integration Connected event. Search the provider by the synthetic device ID shown in UserGist. If UserGist says accepted but the event is not visible immediately, allow a short provider processing delay and confirm the selected data region.