Retry Handling

Cresora automatically retries webhook deliveries that don't receive a 2xx response. Your receiver must handle retries gracefully.

Retry schedule

After 72 hours of consecutive failures, the delivery is marked failed and Cresora sends a webhook.delivery_failed meta-event to your notification email.

What triggers a retry

• HTTP response with any non-2xx status code (including redirects — do not redirect)
• No response within 30 seconds (timeout)
• Connection refused or DNS resolution failure

Idempotent retry handling

Because Cresora retries, your handler will receive the same event multiple times. Always handle events idempotently:

import crypto from "node:crypto";

// Use event.id as an idempotency key
async function handleWebhookEvent(event) {
  // Check if we've already processed this event
  const existing = await db.processedEvents.findOne({ eventId: event.id });
  if (existing) {
    console.log(`Duplicate event ${event.id} — skipping`);
    return; // Already handled; return 200 anyway
  }

  // Process the event
  await processEvent(event);

  // Record that we've handled it
  await db.processedEvents.insert({
    eventId: event.id,
    processedAt: new Date(),
  });
}

Respond quickly, process asynchronously

Your endpoint must respond within 30 seconds. For complex processing, respond immediately and handle the work in a background queue:

app.post("/webhooks/cresora", async (req, res) => {
  verifySignature(req); // Throws on invalid signature — respond 400
  res.sendStatus(200);  // Respond immediately
  await queue.enqueue(req.body); // Process asynchronously
});

Manual replay

You can manually replay any webhook delivery from the Partner Portal:

1. API Settings → Webhooks → Delivery Log
2. Find the failed delivery
3. Click Replay

Replayed events have the same id as the original — your idempotency logic will correctly deduplicate them.