Network-AI
Field note

Field Notes from an Approval That Expired at the Worst Time

Published 2026-10-10 | Expiry timing

An approval expired mid-execution during a long migration, and the workflow had no defined answer for authority vanishing halfway through a committed sequence.

The approval was valid when the migration started and expired forty minutes into it. Half the steps had run under authority; the other half stood in a corridor with no rule for what came next.

The rules that now exist

  • Approvals declare whether they cover initiation or full duration.
  • Long workflows checkpoint before authority-sensitive phases.
  • Expiry mid-flight parks the work at the checkpoint and pages the approver.

Use the AuthGuardian, architecture guide, and audit schema to give mid-execution expiry a designed answer before it happens.

Continue evaluating

Decide what mid-flight expiry means.

Use the AuthGuardian, architecture, and audit schema docs to define how running work behaves when its authorization expires mid-flight.

AuthGuardian Architecture Audit schema