Can someone explain how the Fynd platform manages webhook failure handling and retries, and how the status of events and subscribers affect this process?
2 Likes
When an event occurs, the webhook service on the Fynd platform notifies the subscribed users and marks the event as SUCCESS. However, if the event fails to reach the subscribers, its status is marked as FAILED and the attempt count is incremented. These failed events are retried until 48 hours or 20 attempts are reached. Post this, the event is marked as DISABLED, which also blocks the particular subscriber and marks all their remaining events as RESYNC.
In the case of event statuses, SUCCESS denotes that the event has been successfully communicated, FAILED if unsuccessful, RESYNC if it is pending reattempt after subscriber unblocking and DISABLED if the max limit for retries is reached.
The subscriber can have three statuses: ACTIVE when it is participating in the webhook processing, INACTIVE when it is paused from processing, and BLOCKED when any related event has exhausted its max threshold limit causing all successive events to be marked as RESYNC.
For more details, refer to the Fynd documentation.
3 Likes