Working with event destinations
A destination is a delivery target for a notification. In other contexts, destinations are also called channels, sinks, or consumers.
Destination categories
Destinations are of two categories: human and service.
Human destinations
Human destinations are devices, servers, or applications that present notifications for human consumption. The following human destinations are supported by the Event Notifications service:
The Inbuilt Email and Inbuilt SMS destinations are provided out of the box, and are available whenever you create an instance of Event Notifications. Other destinations must be added manually and require configuration.
Service destinations
Service destinations are cloud services or application where notifications are consumed programmatically. The following service destination is supported by the Event Notifications service:
Retry policy for destinations
When sending notifications to destinations, issues such as network errors and application glitches can cause requests to fail. Event Notifications automatically retries failed requests to provide resiliency.
Retry behavior
The client automatically retries failed requests up to 3 times with a exponential delay between 1 and 10 seconds to prevent retry spikes.
If the destination server returns a Retry-After header, that value (in seconds) overrides the default backoff delay.
Each request has a 10-second timeout, and retries stop immediately once a request succeeds or the maximum attempts are reached.
If a notification fails even after all retry attempts, the notification is lost.
This retry policy applies to the following destinations: