Configuring Idempotent Key
Configure idempotent keys in workflows to prevent duplicate notification events and safely handle retries without triggering the same action multiple times.
Workflows now supports idempotency, ensuring you can safely retry requests without the risk of performing the same operation twice. This feature proves invaluable in scenarios where an API call gets interrupted in transit, leaving you without a response.
For instance, if a request to send a notification doesn't go through due to a network glitch, simply retry the request using the same idempotency key. This guarantees that no more than one notification will be sent.
You can read more about it here.
Steps to configure Idempotent Key
1
After adding a notification event to the workflow, click Settings icon on the top right corner.
2
Navigate to Idempotent tab and add the below details:
- Idempotent Key - Add an idempotent key to prevent this notification event from getting fired multiple times (for a specific duration) to a user when there is no change in the data. Duration should be between 1 second and 24 hours.
- Time - Enter how long you want to prevent duplicate notification events from sending.
- Units - You can add time in Seconds, Minutes, Hours or Days.
We don’t have a length limit for idempotency key but we recommend using 256 characters or less for idempotency key. These keys are purged from the system after 24 hours.