Docs / Strand / resources/data-retention

Data Retention

Strand keeps your run history for a period set by your plan. Older runs are removed automatically by a daily sweep.

Retention is a maximum age, not a guarantee of deletion at that instant: the sweep runs once a day, so runs may persist a few hours past the window.

What the window covers

Your plan's window applies to completed runs and their step records: the inputs, outputs, and errors captured for each node.

It does not apply to:

• Runs that have not finished. A run that is still executing, queued, or

waiting on a human approval is live work, not history, and is never swept however old it is. This matters for approval steps: approval links are valid for 7 days by default and can be configured longer, so a run awaiting sign-off survives past a short retention window.

• Your workflows themselves. Definitions, versions, connectors and vault

entries are not time-limited. Only run history expires.

Usage and billing are not affected

Deleting a run does not un-bill it. Your monthly run count and compute-unit totals are preserved when history is swept, so quota enforcement and invoices stay correct regardless of how much history your plan retains.

Upgrading and downgrading

Upgrading extends the window from that point forward. It does not restore runs already removed.

Downgrading keeps your previous longer window for 30 days. Upgrading again during that period cancels the countdown.

If you need run history preserved beyond your window, contact support during those 30 days and we can export it for you.

Related

• Pricing: current plans and windows
• Contact data retention: the equivalent

for message history

← Back to Strand docs