Manual Webhook Retry
Use manual retry to redeliver one or more webhook events from Webhook Logs. This is useful after you fix an unavailable endpoint, authentication failure, timeout, or other delivery issue.
Retry a failed delivery
- Open Webhooks in the SimZ portal.
- Keep the Failed status filter selected, then narrow the results by webhook, event, date range, or search if needed.
- Retry the delivery:
- Select one or more delivery groups and click Retry selected.
- Click Retry on a failed delivery to resend only that group.
- Click Retry all matching to resend every delivery group that matches the current filters.
- Review the confirmation summary, including the number of eligible and skipped delivery groups when shown.
- Acknowledge that duplicate deliveries may occur, then click Redeliver.
- Monitor the redelivery batch until it completes. The delivery logs refresh when processing finishes.
Retrying successful deliveries
The Webhook Logs page defaults to failed deliveries. To redeliver successful events, change the status filter to Success or All Status. You must confirm an additional warning because the receiving system may already have processed those events.
Redelivery behavior
- SimZ resends the original webhook payload.
- The current webhook URL, headers, signing secret, timeout, and retry count are used.
- Inactive webhooks, deliveries with an unknown event, and deliveries above the batch limit are skipped and shown in the preview.
- Manual redeliveries appear in the logs with a Redelivery label and can be found with the Redeliveries only trigger filter.
- A redelivery creates a new delivery group; it does not modify the original delivery record.
- Redelivery requests include
X-SimZ-Redelivery: true,X-SimZ-Original-Delivery-Group-ID, andX-SimZ-Redelivery-Batch-IDheaders.
When Retry all matching has no From date, SimZ searches the previous 30 days. A redelivery batch can contain up to 1,000 eligible delivery groups.
Prevent duplicate processing
Manual retries can deliver an event your application has already processed. Make webhook handling idempotent and deduplicate events using stable payload fields such as event, callId, companyId, and agentId.
