Failed Deliveries

If Cresora cannot deliver a webhook after 72 hours of retries, the delivery is marked failed.

Failure notification

When a delivery fails permanently, Cresora fires a webhook.delivery_failed meta-event to:

• Your notification email (configured in Partner Portal → Account → Notifications)
• Any other webhook endpoints registered for meta-events

What to do when a delivery fails

1. Check the delivery log

Partner Portal → API Settings → Webhooks → Delivery Log shows every delivery attempt, response status, and the full response body your endpoint returned.

Common causes:

• Endpoint returned 5xx consistently (server error in your handler)
• Endpoint was unreachable (server down, DNS misconfigured)
• Handler took longer than 30 seconds to respond

2. Fix your endpoint

Address the root cause — fix the bug, restore the server, or update the endpoint URL.

3. Replay the failed delivery

Once your endpoint is healthy, replay the event from the delivery log:

Delivery Log → find the failed event → Replay

You can replay individual deliveries or bulk-replay all failed deliveries for a time window.

4. Reconcile missed events

If payments were processed during the outage, reconcile by querying the Payments API directly:

GET https://api.cresoracommerce.com/v1/payments?created_after=2026-05-29T00:00:00Z
Authorization: Bearer csk_test_xxxxxxxxxxxx

Process each payment you may have missed and update your system accordingly.

Disabling a degraded endpoint

If your endpoint has a consistently low success rate (below 80%), Cresora sends a webhook.endpoint_degraded alert. If the issue isn't resolved, Cresora may pause delivery to that endpoint to prevent retry storms. Delivery resumes automatically once the endpoint health improves.

You can manually pause and resume endpoints in the Partner Portal under API Settings → Webhooks.