Shipfolder demo. All sample content on this page is fictional.

Introducing event replay

Re-send any past event to any endpoint, from the dashboard or the CLI.

Author name (placeholder)
Example Co
Diagram of three event boxes joined by arrows, showing an event being sent again to a second endpoint.
Replay sends a stored event again, unchanged.

Placeholder article. This post shows the typography you get for long-form writing: headings, lists, quotes, code and images. Replace it with your own story.

Why replay matters

Endpoints fail. A deploy goes wrong, a certificate expires, a database runs out of connections. When that happens, the events you missed are still important.

  • Recover from outages without asking anyone to re-trigger anything.
  • Send real historic events to a new endpoint while you test it.
  • Debug a handler with the exact payload that broke it.

How it works

Every event is stored for the length of your log retention. A replay creates a new delivery attempt with a fresh signature and the original body:

retry.js
const delay = Math.min(base * 2 ** attempt, cap);
const jitter = Math.random() * delay * 0.2;
schedule(event, delay + jitter);

Placeholder pull quote. Use it for the one sentence you want skimmers to remember.

Limits

You can replay up to 10,000 events in one batch. Larger replays are split automatically.

Try it

Event replay is available on every plan today. Read the quick start or see the release notes.