GitHub Actions retention days: keep the Sume job id elsewhere

The default GitHub Actions retention is 90 days, and from 1 October 2026 checks, workflow runs and statuses follow that same setting. If a workflow log is the only place your Sume job_id was written, that record can disappear. Write the job id and the media.sume.com URL to a store you control when the job is submitted.

GitHub facts are from its changelog; Sume facts from Jobs and results and Asset library. Both read 2026-09-30.

What changes on 1 October 2026?

The changelog says checks, workflow runs and statuses will be governed by the same retention settings that control artifacts and logs, with a default of 90 days. Today, checks and statuses persist for 400+ days regardless of configuration. Public repositories have a maximum 90-day retention limit. The change is not retroactive: previously deleted data cannot be restored.

A companion changelog entry dated 2026-09-24 says expired artifacts are no longer shown in the workflow run summary page or the REST API artifact listing, although run logs still contain information about artifacts after expiration.

Why does this matter for a Sume job?

Sume's docs say generation endpoints create durable jobs, and to store the job id from the submit response so your integration can recover work after process restarts. A CI run is a process that ends. If the job id lives only in its log, recovery depends on how long GitHub keeps that log.

The job and its result are on Sume's side: GET /v1/jobs/:id/result returns the result, and GET /v1/jobs/:id/events returns what the docs call a public timeline for debugging and recovery.

What should the workflow store, and where?

Store two things per generated file in your own database, repository file or release notes: the job_id from submit, and the Sume URL from the result. The asset library docs say integrations should store the Sume URL, not raw provider URLs.

Keep the same Idempotency-Key you used for the submit next to the id, so a re-run of the job step reuses it; re-running a workflow without double-billing covers that, and idempotency keys for AI video APIs explains the rule.

Is this the same as a Sume retention limit?

No. The 90-day figure is GitHub's. This post does not state how long Sume keeps any job or file; check the cited docs pages for that. A similar pattern on another platform is in Cloudflare Workflows retention and Sume job ids.