Skip to content

docs: correct data retention for runs and storages - #3233

Open
TC-MO wants to merge 5 commits into
masterfrom
docs/data-retention
Open

TC-MO wants to merge 5 commits into
masterfrom
docs/data-retention

Conversation

@TC-MO

@TC-MO TC-MO commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

Runs and builds still claimed the 10 latest runs are kept indefinitely and linked to a pricing page with no retention info, contradicting the Storage page that #2089 fixed. This aligns Runs and builds, the storage callouts, and the limits API description with the actual plan-based retention.

Runs and builds still said the 10 latest runs are kept indefinitely,
which contradicts the Storage page and is wrong on paid plans.
@TC-MO TC-MO added documentation Improvements or additions to documentation. t-docs Issues owned by technical writing team. labels Nov 16, 2026
@TC-MO TC-MO self-assigned this Nov 16, 2026
@apify-service-account

apify-service-account commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

❌ Preview build for this PR (commit 16be36a) failed. See action run for details.

@apify-service-account

Copy link
Copy Markdown
Contributor

API behavior and specification alignment:

Reviewed commit: 3cec5a5

Free plans keep the 10 most recent runs for up to 4 months past the
retention period, so "deleted when the period ends" was wrong there.
@apify-service-account

apify-service-account commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

API behavior and specification alignment: Aligned.

Reviewed commit: 16be36a

@TC-MO
TC-MO marked this pull request as ready for review November 20, 2026 15:07
@janbuchar
janbuchar removed their request for review November 20, 2026 22:42

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation. t-docs Issues owned by technical writing team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants