Learn about the lifecycle of an event in Numeral
Events have their own statuses and lifecycle. Unlike all other Numeral objects, events do not trigger the creation of events.
Statuses
| Status | Description |
|---|---|
| created | Event has been created. |
| delivered | Event has been sent and successfully delivered to the configured webhook(s). A 2xx HTTP status code is expected. |
| pending_retry | Event has been sent to the configured webhook(s), but at least one delivery was not successful, due to an HTTP status code different from 2xx or no response at all. The event will be re-sent up to 5 times, using an exponential back-off strategy. The maximum duration of the back-off strategy is ~2.8 hours. |
| failed | Event is set to failed status after 5 unsuccessful deliveries. It can be retried via the API or manually from the dashboard. Learn more here. |
| archived | Event is automatically archived if no webhook is configured for this event topic or type. Events that have been archived events can be manually retrieved using the Numeral API. |
State machine
