TestFlight rate limit hit mid-release-notes-generation: agent failed with error 429 too many requests

TL;DR

When an agent run to generate release notes hits this failure - failed with error 429 too many requests - do not retry the same step blindly. First check the real state in TestFlight to learn whether the step already took effect, then slow the workflow down and make it resumable: honour retry delays, add exponential backoff with jitter, batch or cache status reads, and record completed sub-steps so a throttled run resumes instead of restarting and re-hammering the API. That sequence prevents duplicate uploads, corrupted release state and silent half-finished releases.

TestFlight rate limit hit mid-release-notes-generation: agent failed with error 429 too many requests

Use this when

• An automated release run to generate release notes failed with this pattern.
• The workflow uses TestFlight and the failure appeared mid-run, after earlier steps may already have applied.
• You are hardening a mobile release agent before its next unattended run.

Not for this skill when

• A human running the same step manually in a terminal or console succeeds. That points at the underlying tool, not the agent wrapper.
• The store rejected the release on policy or metadata grounds. That is a store review issue, not an agent reliability failure.

Steps

1. Pause the workflow and note which call in TestFlight returned 429 and how many calls the run made in the preceding minutes. Verify: the throttled endpoint and the recent call volume are identified
2. Check whether the throttled step partially applied by reading the store state once, after a wait, rather than immediately retrying. Verify: the true state is known before any retry is planned
3. Implement exponential backoff with jitter for this API, starting around a minute and doubling, and respect any retry delay the response headers give. Verify: the workflow code or configuration shows the backoff policy
4. Reduce call volume: poll status less often, batch asset operations, and cache reads that do not change during the run. Verify: the planned call count for a full run is measurably lower than before
5. Persist completed sub-steps so a throttled run resumes where it stopped instead of restarting and repeating calls. Verify: the state file lists completed sub-steps after a stopped run
6. Resume the run to generate release notes at the reduced pace. Verify: the run completes with no further 429 responses
7. Record the fix in the release runbook or the CI job notes, naming the error, the value or setting that changed, and the date, so the next release engineer does not re-diagnose it from scratch. Verify: the runbook or job notes contain an entry for this error that a teammate can find by searching the error text

Why it happens

Store APIs enforce per-account and per-app rate limits, and release workflows burst exactly when they hurt most, polling status and uploading many assets at once. A 429 is the API asking for pace, and immediate retries deepen the throttle window.

In practice this failure is rarely a one-off. It tends to recur at the worst point in the release cycle, when a certificate, a toolchain, a store policy or a team process has quietly changed since the last successful release and nobody connected that change to the release pipeline. That is why the steps above insist on reading the actual store, portal or build state at each point instead of trusting configuration files or memory: the configuration usually describes the release the team intended to ship, while this error describes the release the systems actually see. Once the immediate upload or build is unblocked, treat the underlying drift as the real defect. Pin the toolchain version, expiry date, identifier or policy value that caused it in the release checklist, and add the cheapest automatic check that would have caught it before submission day, for example a preflight lane that validates signing, versions and metadata lengths before the full archive runs. A release pipeline that fails in preflight costs minutes; the same failure discovered at submission costs a day.

Variants and edge cases

agent failed to generate release notes reliability playbook

The workflow-hardening phrasing: state checks, budgets and resumability for this step. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

TestFlight agent workflow failure recovery

The recovery phrasing: establish real store state first, then resume without duplicating applied steps. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Edge case: partial application

The hardest variant of every agent failure is the half-applied release. Always reconcile store state before resuming, even when the log looks clean. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstJq75ZBmDszIGQLBiUnWcw