## TL;DR
When an agent run to monitor the rollout hits this failure - failed with error 401 unauthorized - do not retry the same step blindly. First check the real state in the release API to learn whether the step already took effect, then refresh or replace the credential before the run, not during it: check the credential expiry at workflow start, fail fast with a clear message if it is expired, and prefer long-lived API keys or service accounts over short-lived session credentials for unattended release runs. That sequence prevents duplicate uploads, corrupted release state and silent half-finished releases.

```text
auth token expired mid-rollout monitoring run: agent failed with error 401 unauthorized
```

## Use this when
- An automated release run to monitor the rollout failed with this pattern.
- The workflow uses the release API 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. Identify which credential the failing call in the release API used and when it expires, from the secret store or key record, not from the error alone. Verify: the credential type and its expiry are known
2. Check the store state for which earlier steps applied before the 401, so the release is not left half-submitted unknowingly. Verify: applied and pending steps are listed from a fresh read
3. Replace short-lived session credentials with a long-lived API key or service account where the store offers one, stored in the secret manager. Verify: the new credential authenticates on a read-only call
4. Add a start-of-run credential check that verifies validity and remaining lifetime and fails fast with a clear message before any store change. Verify: a test with an expired credential stops at step zero with that message
5. Make the workflow resumable from the state file so a credential fix does not require repeating applied steps. Verify: the state file records each completed step
6. Resume the run to monitor the rollout with the fresh credential. Verify: the run completes with no 401 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
Release runs are long, and credentials minted at the start can expire mid-run; session-based credentials also die when passwords change or two-factor is re-challenged. A 401 mid-run leaves earlier steps applied and later steps blocked, the worst state for a release.

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 monitor the rollout 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.
### the release API 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/pst_hopIKX0m7ku6DHlmgZO4iw