Pipedream keeps events 7 days on Free: store Sume job ids elsewhere

Pipedream's limits page says the free tier keeps 7 days of events, and execution details expire after 365 days (Pipedream limits, read 2026-10-02). A Sume video job can be queried long after that, so save the job_id in a store you own at submit time rather than relying on the event history.

Limits the page lists

The page also says these limits can change at any time and points to the pricing page for plan details, so re-read it before relying on a number.

What Sume keeps

A Sume job is durable once accepted. GET /v1/jobs/{job_id}, /status and /result read it, and /events gives a timeline including webhook.delivery. List calls return only jobs that your key's member created. The docs do not publish a retention period for job records, so do not treat Sume as a long-term archive either.

A small ledger in the workflow

• After the Sume submit step, write job_id, a business key (such as a row or order id) and the time to a database or Data Store.
• In the webhook workflow, verify the signature, then update that row with status and result URL.
• Respond with 2xx quickly. Sume gives each webhook attempt 10 seconds.
• Dedupe on job_id, since a retry or a Redeliver sends the same terminal event again.

Why the ledger beats the event view

When a customer asks about a render from three weeks ago, a free-tier Pipedream event history is gone. A ledger row with the job id lets you read the job from Sume directly, and a Redeliver call re-sends the terminal event if you need the payload again, as long as the job record is still readable.