A complete retry cycle — webhook fires, endpoint fails, the plugin queues exponential-backoff retries, endpoint recovers, re-delivery succeeds. All visible in the Event Log.
This screencast captures a complete webhook retry cycle using Webhook Actions by Flow Systems. The sequence begins with a webhook delivery attempt to an endpoint that is temporarily unavailable — the plugin logs the failure with the HTTP error code and response time.
Rather than dropping the event, the plugin persists it to the queue and schedules automatic retries using exponential backoff: the first retry fires 1 minute after the initial failure, the second after 2 minutes, then 4, 8, and 16. Each attempt is logged independently so you have a full audit trail.
When the endpoint comes back online, the retry succeeds — the Event Log entry updates to HTTP 200 with the response body, and the event is marked as delivered. No manual intervention required. This behavior runs on Action Scheduler, so it survives server restarts and does not block the main PHP thread.
The replay button lets you re-send any logged delivery on demand, whether it was a failure or a success, without re-triggering the original WordPress action hook.
Deep-dive into the retry and replay architecture → WordPress Webhook Retry and Replay System