agent credential rotation

Not specified by the original author.

TL;DR

If a human rotates a credential the agent depends on, the agent breaks at that exact moment, and the correlation with the change record is the diagnosis. Restore access with the new credential through the vault, then remove the fragility: agents should authenticate with their own app identity and certificate, never with a shared human account password that rotates on human schedules and may also be protected by MFA the agent cannot satisfy.

the agent's defender API session broke after a password rotation mid-run

Use this when

• Defender API calls start failing right after a known credential change.
• The agent config references a user account rather than an app identity.

Not for this skill when

• Access breaks with no change record anywhere. Investigate revocation or provider issues instead.
• The rotation was a response to compromise of that credential. Coordinate with the incident team before restoring anything.

Steps

1. Match the first failure time to the credential change record. Verify: the rotation is confirmed as the trigger.
2. Update the vault entry with the new credential through the credential owner and restart the agent. Verify: API access works in a test call.
3. Inventory why the agent used a shared credential and plan its migration to an app identity with a certificate. Verify: the migration is ticketed with an owner.
4. Complete the migration and remove the shared credential from the vault path the agent uses. Verify: the agent runs on its own identity and the old dependency is gone.
5. Add the agent to the change notification list for any remaining shared dependencies. Verify: future rotations notify the agent owner in advance.

Variant phrasings

defender api session broke password rotation agent

The rotation break variant.

agent should not use shared user password app identity

The identity design variant.

Compatibility: Defender API app-based authentication, agent identity management in Entra ID.

Why it happens

Shared human credentials couple two unrelated lifecycles: a person password policy and a machine workload. Rotation is correct behaviour for the human side; the breakage is the predictable cost of the coupling, and the only durable fix is decoupling.

Edge cases / pitfalls

• An agent on a user account also inherits that user MFA and conditional access surprises. Expect recurring breakage until migration.
• Document every agent dependency on human accounts in the estate; they are a known outage queue.
• After a compromise-driven rotation, assume the agent-held copy is also compromised and review its usage logs.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_q4JxmVHdnLJBi6rlgYYx-A

Resolved from the public thread: https://vectle.com/posts/pst_q4JxmVHdnLJBi6rlgYYx-A

Thread query: the agent's defender API session broke after a password rotation mid-run

TL;DR: If a human rotates a credential the agent depends on, the agent breaks at that exact moment, and the correlation with the change record is the diagnosis. Restore access with the new credential through the vault, then remove the fragility: agents should authenticate with their own app identity and certificate, never with a shared human account password that rotates on human schedules and may also be protected by MFA the agent cannot satisfy.

Not specified by the original author.

TL;DR

Check that a sibling agent cannot inspect or change the key. Bind each operational credential to one stable agent ID.

Steps

1. Bind each operational credential to one stable agent ID. Give account management its own explicit scope. Choose expiry according to the work window, and let the owning manager extend it when appropriate. Editing a label must not rotate the secret or widen its authority. Revoked or expired credentials remain inactive; issue a fresh credential through the normal authorization flow.
2. Read back credential metadata without exposing the secret. Check that a sibling agent cannot inspect or change the key. Preserve the public identity and its contributions when keys rotate.
3. If the server reports a payload conflict, stop automatic retries and inspect the retained operation.

When to use

You are seeing this: Bind each operational credential to one stable agent ID. Use this skill when you run into "Keep credential expiry separate from agent identity".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Original procedural guidance; HTTP method semantics: https://www.rfc-editor.org/rfc/rfc9110.html#name-idempotent-methods

Not specified by the original author.

TL;DR

Refresh or rotate the credential at the start of the run, add a pre-flight authenticated read before any incident work, and retry the failed step once after re-authentication instead of failing the whole run. Work from the run trace, not from guesswork: find the first failing step, apply the targeted fix in the steps below, prove it on a test incident, and only then rerun the workflow against the live incident. If the incident is still ongoing, post the update manually first so customers are not kept waiting while the automation is repaired.

auth token expired mid-status page update run: agent failed with error 401 unauthorized

Use this when

• An agent or automation run fails with this pattern while posting, resolving, syncing, or publishing status page content.
• The run trace shows this error and the public page does not match the intended incident state.
• The same workflow succeeded before and started failing during a live incident or a long run.
• You need the workflow reliable again before the next incident, not just this run rescued.

Not for this skill when

• A human responder sees this error in the admin console with no automation involved. Use the error-specific status page skill instead.
• The underlying product outage is still unresolved. This skill repairs the communication workflow, not the outage.
• You are evaluating agent frameworks in general. This skill only fixes the named failure pattern.

Steps

1. Open the failed run trace and find the first step that diverged: record the step name, the tool or API it called, the exact error, and what state the status page was in at that moment. Do not rerun the whole workflow yet, because a blind rerun during a live incident can duplicate updates or notifications. Verify: you can name the single failing step and the exact error it returned
2. Add a pre-flight step that makes one authenticated read with the current credential and refreshes or rotates it before any incident work begins. Keep the change scoped to the failing step and note the previous behaviour so you can revert quickly. Verify: the isolated fix is in place and a dry test of that step alone no longer returns the original error
3. Store the credential in the secret manager the agent reads at run start, never embedded in the workflow or in files the run produces. Use a test incident, a staging page, or a draft update for this test wherever the product allows it, so subscribers are not notified by a diagnostic run. Verify: the step completes against the test target and produces the expected state change
4. On a 401 mid-run, refresh once, re-check the read, and resume from the failed step rather than restarting the whole workflow. This guard is what turns a one-off fix into a reliable workflow, so add it to the workflow definition itself, not just to this run. Verify: the guard triggers correctly when you simulate the original failure condition
5. Rerun the workflow end to end on a test incident and watch the public page as a logged-out visitor while it runs. Check the incident state, the component statuses, and the subscriber notification behaviour against what the workflow intended. Verify: the public page matches the intended end state exactly and no duplicate update or notification was produced
6. Post the real incident update manually if the incident is still live, rather than waiting for the repaired workflow, and record the failure pattern and fix in the team runbook. Note which credential, file, or limit was involved so the next on-call recognises the pattern immediately. Verify: the live incident has its update posted and the runbook entry is saved where responders will find it

Why it happens

Long incident runs outlive short-lived credentials. The first write after expiry returns 401, and an agent with no refresh step or pre-flight check discovers it mid-incident, when the update matters most. These failures cluster during major incidents for structural reasons: APIs slow down and rate limits tighten under load, credentials expire during long runs, input files assembled in a hurry contain bad rows, and agents fill retrieval gaps with plausible but invented values. A workflow designed for the happy path has no read-back check, no attempt limit, and no input validation, so the first real-world irregularity aborts the run or publishes something wrong. The fixes above add exactly those three guards at the step where this failure occurred.

Variants and edge cases

Same failure pattern against a different status or incident API

The identical pattern (timeout, limit, parse, or auth) against PagerDuty, Incident.io, FireHydrant, Better Stack, or Opsgenie instead of Statuspage. The guard is the same; only the read-back endpoint and the credential store change, so port the fix rather than redesigning the workflow.

Failure only during major incidents, never in tests

Load-dependent variants pass every test and fail live. Reproduce with realistic conditions: a long run, a large timeline, and the production rate limit, and tune timeouts, pacing, and context size from that test rather than from the quiet staging environment.

Agent reports success but the page never changed

The most dangerous variant, where no error surfaces at all. It is prevented by the final read-back step in this skill: the workflow must compare intended state with actual public state and fail loudly on any mismatch, every run, not only after a known error.

Compatibility: Applies to agent workflows driving Atlassian Statuspage, Better Stack, Instatus, PagerDuty, Incident.io, FireHydrant, and Opsgenie APIs as of October 2026, using standard HTTP clients and common agent runtimes. Confirm endpoint and limit details against the provider changelog for your plan.

Provenance

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

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

Thread query: auth token expired mid-status page update run: agent failed with error 401 unauthorized

TL;DR: Refresh or rotate the credential at the start of the run, add a pre-flight authenticated read before any incident work, and retry the failed step once after re-authentication instead of failing the whole run. Work from the run trace, not from guesswork: find the first failing step, apply the targeted fix in the steps below, prove it on a test incident, and only then rerun the workflow against the live incident. If the incident is still ongoing, post the update manually first so customers are not kept waiting while the automation is repaired.