Exceptions and reversals
What goes wrong, and how is it undone?
The happy path is where demos live. Exceptions are where operations, cost and customer trust live. Every industry has a catalog of things that go wrong and a formal way to undo each one.
What it is
Exceptions are the predictable ways a process fails: rejections, disputes, corrections, fraud. Reversals are the formal ways to undo an outcome, usually with deadlines, evidence requirements and someone else's approval.
Most of the cost of running a regulated product sits in the exception paths, not the happy path.
Where you'll see it
| Industry | Exceptions and reversals |
|---|---|
| Payments | Chargebacks, refunds, returned bank transfers |
| Healthcare | Claim denials, appeals, resubmissions |
| Telco | Blocked messages, rejected registrations, failed number ports |
| Payroll | Off-cycle payments, corrections, reversed deposits |
| Insurance | Disputed claims, rescinded policies |
Questions to ask in week one
- What are the five most common exceptions, and how often does each one happen?
- Which can we fix ourselves, and which need a counterparty?
- What deadlines apply to each reversal, and what evidence does it need?
- Who notices the exception first: us, the customer or their end user?
- What does each exception cost us in time and money?
The trap
Designing the happy path first and adding exceptions later. In regulated industries the exception flow is often the product customers judge you on, because it's the moment they need you most.
In the Field Guides
AI agents: orchestration platforms
There are two kinds of reversal: roll back the agent, or reverse what it did. Only the first is a deploy.
Rate limit or outage
- Who starts it
- The lab
- Clock (as of Oct 2026)
- Retry-after; none at a spend cap
- The way back
- Back off, or fall back to a model that behaves differently
Timeout after the target committed
- Who starts it
- The network
- Clock (as of Oct 2026)
- Seconds
- The way back
- Retry with the same idempotency key; without it, a duplicate
Loop hits a cap
- Who starts it
- The runtime
- Clock (as of Oct 2026)
- Turns, budget or timeout
- The way back
- Stop or escalate; the tokens are already billed
Model retired mid-run
- Who starts it
- The lab or cloud
- Clock (as of Oct 2026)
- 45 days to 6 months' notice
- The way back
- Pinned snapshot until the date, then re-evaluate
Wrong but authorized action
- Who starts it
- The agent
- Clock (as of Oct 2026)
- Immediately
- The way back
- A compensating call to the target's API, if one exists
Malicious MCP server found
- Who starts it
- A researcher or registry
- Clock (as of Oct 2026)
- After the fact
- The way back
- Revoke tokens; manual takedown; no protocol kill switch
Poisoned memory
- Who starts it
- Rarely anyone
- Clock (as of Oct 2026)
- Any time
- The way back
- Roll back memory; purge index and traces
Some actions nobody can reverse. In July 2025, Replit's coding agent deleted a user's production database during a declared code freeze, then misreported what it had done; Replit then split development from production by default. In late 2025, Google's Antigravity coding tool ran a recursive delete on a whole drive partition instead of a cache folder.
Redeploying the old agent doesn't unsend an email or reverse a refund, which is why every write tool needs an idempotency key, a logged action history and, where possible, a compensating action.
AI coding agents: writing, reviewing and shipping code
Bad change merged
- Who starts it
- The team, after an alert
- Clock
- Minutes to days
- The way back
- Git revert; feature flag off
Data deleted by an agent
- Who starts it
- The agent, with real credentials
- Clock
- Immediate
- The way back
- Backups outside the blast radius, if they exist
Secret leaked in a commit
- Who starts it
- The agent or the developer
- Clock
- Immediate
- The way back
- Rotate it; history keeps it
Malicious package published
- Who starts it
- An attacker with a stolen token
- Clock
- Hours
- The way back
- Deprecate the version; downstream lockfiles keep it until changed
Model supply cut
- Who starts it
- The lab
- Clock
- Under a week (Windsurf, 2025) to about 75 days (Cursor, as reported)
- The way back
- Another model, or your own key with the lab (Windsurf's users kept Claude that way)
Price or limit change
- Who starts it
- The vendor
- Clock
- Weeks; promotions just end
- The way back
- Caps, routing, another vendor
Training default changed by a policy update
- Who starts it
- The vendor
- Clock
- The policy's start date
- The way back
- Opt out again; data already used can't be taken back out of a model, as far as I know
AI evals and observability: how teams measure AI quality
| Exception | Who starts it | What happens |
|---|---|---|
| Blocked at the gate | The suite | Triage: real regression, eval bug, judge noise or an accepted trade-off |
| Passes offline, fails on the rollout slice | Real traffic | Stop widening; add the failing traces to the test set; re-run |
| Rolled back after an incident | Users, support or monitoring | Revert the bundle; check caches and actions already taken; write the test case first |
| Forced change by the provider | Retirement notice, alias move, removed parameter | A model upgrade with a deadline |
| Judge changed or retired | The provider or your team | Re-score a human-labelled anchor set; mark old and new scores as not comparable |
| Eval tool shut down or sold | The vendor | Export datasets and results before the deadline |
Reversal is easy for prompts and model pins and hard for everything else. A retired model can't be rolled back to, and agent actions stay done: in July 2025 Replit's coding agent ran destructive commands on a customer's database during a code freeze, and the fix afterwards was separating development from production. Compensation is close to nonexistent. After its April 2026 postmortem Anthropic reset subscribers' usage limits; I found no lab credits or refunds to builders for degraded quality after any incident.
AI governance and model risk
| Exception | Who starts it | What happens |
|---|---|---|
| Use before validation | The business, for urgent need | Allowed under US bank guidance with limits and closer monitoring; the conditions may never close |
| Out of scope by definition | The guidance | A US bank's generative AI isn't a "model"; each bank decides whether to validate it anyway |
| Use beyond intended purpose | The business | New analysis; in the EU, repurposing into a high-risk use makes you the provider |
| Vendor won't share internals | The vendor | Behavior tests, outcome monitoring, contract terms on change notice and audit |
| Forced change from outside | Lab retirement, cloud auto-upgrade, a settlement | Unplanned re-testing and re-approval |
| Rejected use case | The governance team | Often continues on personal accounts |
| Incident | Monitoring, a complaint, a regulator | Contain, notify, find the cause; EU high-risk providers report serious incidents within 15 days |
| Rule reversed | A government or court | CFPB circulars withdrawn, EEOC guidance removed, an FTC order set aside, Illinois rules withdrawn, Italy's fine on OpenAI annulled |
A rule withdrawn in Washington doesn't remove the statute behind it, and states and private plaintiffs can still sue.
Agent identity and delegated access: how AI agents act for people
| Exception | The way back | Who starts it |
|---|---|---|
| An agent is hijacked mid-task | Revoke its tokens and identity; review what it did | Detection, often an outside researcher |
| An integration vendor is breached | Revoke every token it held; every customer reconnects | The platform (Salesforce, Google) |
| An agent deletes or damages something | Restore from backups the agent couldn't reach | The user |
| An agent buys the wrong thing | A non-fraud dispute, if the card issuer takes it | The user |
| An agent's owner leaves | Move sponsorship or disable the agent | The directory or HR feed |
Revocation is the only remedy that works everywhere, and it comes in bulk: every Drift token, every Asana MCP connection after a June 2025 bug, Klue's whole integration. Undo is often possible but not obvious: when Replit's agent deleted a customer's production database in July 2025, it told the user rollback was impossible, and Replit's CEO later said a one-click restore existed. Payment reversals were designed for payments nobody authorized, which an agent's purchase may not be.
B2B payments: cross-border payouts
Most cross-border exceptions run on someone else's clock and end in a request that can be refused.
Rejected before settlement
- Who starts it
- A bank or the rail
- Clock (as of Oct 2026)
- Same day
- The way back
- Returned, minus fees and any reconversion loss
Wire returned (pacs.004)
- Who starts it
- Beneficiary bank
- Clock (as of Oct 2026)
- Days to weeks
- The way back
- A new FX rate; fees taken twice
Recall (gpi Stop and Recall)
- Who starts it
- Sender
- Clock (as of Oct 2026)
- Clean only before credit
- The way back
- After credit, the beneficiary must agree
SPEI return, closed CLABE
- Who starts it
- Receiving bank
- Clock (as of Oct 2026)
- Immediate
- The way back
- Pesos back in the prefunded account
SPEI or Pix to a wrong valid account
- Who starts it
- The sender's error
- Clock (as of Oct 2026)
- Any time
- The way back
- Only with the recipient's consent; Pix's return mechanism excludes it
Credit delayed, MXN 50,000 or more
- Who starts it
- Receiving bank, with Banxico approval
- Clock (as of Oct 2026)
- Longer, if approved
- The way back
- Wait
Pix precautionary block
- Who starts it
- Receiving institution
- Clock (as of Oct 2026)
- Up to 72 hours
- The way back
- Wait, or the fraud process
OFAC block
- Who starts it
- Bank or provider
- Clock (as of Oct 2026)
- Report within 10 business days
- The way back
- An OFAC licence
Push to the wrong card
- Who starts it
- Originator
- Clock (as of Oct 2026)
- None
- The way back
- No chargeback; the issuer's cooperation
Overpaid wages
- Who starts it
- Payroll
- Clock (as of Oct 2026)
- Next run
- The way back
- Deduction within local limits; CFDI replaced
A logistics company that pays a Mexican carrier MXN 150,000 over SPEI and mistypes one digit of the CLABE can land the money in someone else's valid account. Its bank can ask for the money back, but it returns only if that stranger agrees.
Consumer protections don't reach business payouts. Reg E's error rights are consumer-only, and the UK's push-payment fraud reimbursement (up to £85,000 a claim) covers only transfers between UK accounts. In the euro area, a provider that ran Verification of Payee isn't liable for a credit to the wrong IBAN; one that didn't must refund.
B2B payments: order to cash
Most of an AR team's week is exception work, and every exception runs on its own clock.
Credit hold
- Who starts it
- The seller's ERP
- Clock (as of Oct 2026)
- Hours to days, often with a sales escalation
- The way back
- Release, ship part, prepay, raise the limit, cancel
Invoice rejected
- Who starts it
- Payer AP
- Clock (as of Oct 2026)
- Until fixed; the clock often restarts
- The way back
- Fix and reissue
Dispute or deduction
- Who starts it
- Payer
- Clock (as of Oct 2026)
- Seller's policy; the retailer's deadlines
- The way back
- Case: credit memo if valid; repayment or offset if not; write off small or old ones
ACH return: insufficient funds (R01), account errors (R02 to R04)
- Who starts it
- Payer's bank
- Clock (as of Oct 2026)
- 2 banking days
- The way back
- Reverse the application, re-collect or switch rail
ACH return: business says "not authorized" (R29)
- Who starts it
- Payer's bank
- Clock (as of Oct 2026)
- 2 banking days
- The way back
- Fresh authorization; never retry blindly
Suspect ACH credit returned (R17)
- Who starts it
- Seller's bank
- Clock (as of Oct 2026)
- Nacha fraud rules, 2026
- The way back
- Show your bank KYB evidence
Returned check
- Who starts it
- Paying bank
- Clock (as of Oct 2026)
- Midnight deadline; fraud claims months later
- The way back
- Reverse, reopen, fee, re-collect
Card chargeback
- Who starts it
- Payer's issuer
- Clock (as of Oct 2026)
- Up to 120 days for card-absent fraud; 30-day response cycles (Visa)
- The way back
- Represent with PO, proof of delivery, Level 3 data
Wire, RTP or FedNow recall
- Who starts it
- Payer's bank
- Clock (as of Oct 2026)
- None: a request the receiver can refuse
- The way back
- Voluntary return, or law enforcement
Canadian business PAD claim
- Who starts it
- Payer's bank
- Clock (as of Oct 2026)
- 10 business days; 90 calendar days with no agreement
- The way back
- Debited back to the seller
Unapplied cash
- Who starts it
- Nobody
- Clock (as of Oct 2026)
- Until researched
- The way back
- Suspense or on account, then apply
Customer insolvency
- Who starts it
- Court, trustee
- Clock (as of Oct 2026)
- US: priority for goods received 20 days before filing, reclamation within 45, preferences back 90. Canada: repossess goods delivered in the last 30 days
- The way back
- Stop shipping, file claims, defend preferences, claim on insurance
Card processors set their own chargeback response deadlines, often shorter than Visa's.
Nacha counts R29 toward the 0.5% unauthorized threshold; crossing 3% administrative or 15% overall triggers an inquiry. The clocks are short for business accounts, which is why sellers like pulling from businesses, and why a missed day usually means a lost case.
B2B payments: procure to pay
Most of an AP team's week is exceptions, and once money is released, every rail runs its own clock.
A PO for 1,000 cartons at $4.00 each comes back invoiced at $4.06. With a 2% price tolerance it passes on its own. At $4.20 it lands in the exception queue and waits for the requester, while the 10-day discount window keeps running.
Match exception
- Who starts it
- AP
- Clock (as of Oct 2026)
- Buyer's policy; the discount window keeps running
- The way back
- Tolerance, route to requester, credit memo, wait for receipt
Changed bank details
- Who starts it
- AP or the bank's monitoring
- Clock (as of Oct 2026)
- Before release
- The way back
- Callback to a number on file, account validation, release or block
ACH return: account closed, missing or invalid (R02 to R04)
- Who starts it
- Supplier's bank
- Clock (as of Oct 2026)
- 2 banking days
- The way back
- Fix the vendor master, re-validate, resend
ACH reversal
- Who starts it
- Buyer's bank, for the buyer's own error
- Clock (as of Oct 2026)
- 5 banking days; duplicates and erroneous entries only
- The way back
- Reversing entry
Suspect credit returned (R17), or return requested (R06)
- Who starts it
- Supplier's bank
- Clock (as of Oct 2026)
- Only if funds remain
- The way back
- Recovery if the fraudster hasn't moved the money
Positive Pay exception
- Who starts it
- Buyer's bank
- Clock (as of Oct 2026)
- The bank's daily cut-off; the default is set by agreement
- The way back
- Return the altered or counterfeit check
Lost, stolen or uncashed check
- Who starts it
- Buyer
- Clock (as of Oct 2026)
- Stale after a few months
- The way back
- Stop payment and reissue; void; report as unclaimed property
Virtual card never charged
- Who starts it
- Supplier inaction
- Clock (as of Oct 2026)
- Card expiry
- The way back
- Reissue, or fall back to ACH or check
Wire, RTP or FedNow sent to a fraudster
- Who starts it
- Buyer's bank
- Clock (as of Oct 2026)
- No right of return; hours matter
- The way back
- Recall request; FBI IC3 report
Duplicate already paid
- Who starts it
- AP or a recovery audit
- Clock (as of Oct 2026)
- Supplier goodwill
- The way back
- Credit or refund request
Positive Pay defaults and stale-check periods vary by bank agreement and state law.
APQC's 2020 data put duplicate or erroneous payments at under 1% of disbursements for top performers and 2% for the bottom, usually from duplicate vendor records, a PDF re-sent after the paper copy, a renumbered invoice, or paying from a supplier statement.
With push payments the buyer has no right to take money back. After release every reversal is a request, and for fraud the window is hours.
B2B payments: real-time payments and open banking
Rejected before settlement
- Who starts it
- Either bank or the network
- Clock (as of Oct 2026)
- Seconds
- The way back
- Nothing settled; retry
Held by the receiving bank (US)
- Who starts it
- Supplier's bank
- Clock (as of Oct 2026)
- Next business day on RTP
- The way back
- Released, or refunded as a new payment
Request for return (RTP)
- Who starts it
- Payer's bank
- Clock (as of Oct 2026)
- Answer within 10 banking days
- The way back
- Receiver decides
Return request (FedNow)
- Who starts it
- Payer's bank
- Clock (as of Oct 2026)
- Within 60 days; answer next business day
- The way back
- Receiver decides; a new pacs.004
Fraud claim on Pix (MED)
- Who starts it
- Payer's bank, without judging merit
- Clock (as of Oct 2026)
- Within 80 days
- The way back
- Banks along the trail block; return what's left
UK scam reimbursement
- Who starts it
- Victim
- Clock (as of Oct 2026)
- Claim within 13 months; paid in 5 business days
- The way back
- Sending bank pays; receiving bank repays half
Mistaken payment in the UK or EU
- Who starts it
- Payer
- Clock (as of Oct 2026)
- Best efforts
- The way back
- Banks try to recover; payee details shared
A UK reimbursement is paid whether or not the money comes back; elsewhere, recovery mostly depends on the money still being there. Brazil's tracing process, MED, has recovered little: of R$24.5 billion lost to Pix scams from January 2022 to April 2026, 8.9% was returned, mostly because the fraudsters' accounts were empty by then. Almost all of that predates MED 2.0, which follows money through up to five onward accounts.
B2B payments: spend management
Card exceptions run on network clocks; expense exceptions are conversations with an employee.
Decline: limit, category, prepaid balance
- Who starts it
- Processor or platform
- Clock (as of Oct 2026)
- 2 to 3 seconds
- The way back
- New limit or card; one decline isn't Reg B adverse action
Stand-in approval against policy
- Who starts it
- The network, if the processor is down
- Clock (as of Oct 2026)
- At authorization
- The way back
- None at network level; recover from the employee, or absorb
Forced, late or larger capture
- Who starts it
- Merchant
- Clock (as of Oct 2026)
- Up to the clearing window: 10 days online, 30 for lodging
- The way back
- A dispute; controls can't block it
Refund
- Who starts it
- Merchant
- Clock (as of Oct 2026)
- Within 3 business days of settlement (Visa US), even to a canceled card
- The way back
- Match it to the original sale yourself
Third-party fraud
- Who starts it
- Cardholder, through the issuer
- Clock (as of Oct 2026)
- Visa 120 days; processors sooner; one bank contract 60 days after billing
- The way back
- Chargeback
Missing receipt
- Who starts it
- Expense tool
- Clock (as of Oct 2026)
- Company reminders; the IRS's 60 days
- The way back
- Signed statement plus corroboration; suspend the card
Out of policy or personal charge
- Who starts it
- Approver or audit
- Clock (as of Oct 2026)
- 120 days to repay before it's wages
- The way back
- Employee repays; payroll deductions limited by law
Refund to a personal card after reimbursement
- Who starts it
- Merchant
- Clock (as of Oct 2026)
- Any time
- The way back
- Detect it and recover
Reimbursement ACH returned (R02, R03)
- Who starts it
- Employee's bank
- Clock (as of Oct 2026)
- 2 banking days
- The way back
- Fix the account and resend
Uncashed reimbursement check
- Who starts it
- Employee
- Clock (as of Oct 2026)
- State dormancy rules
- The way back
- Void, reissue, or report as unclaimed property
Two rules surprised me: you can only dispute a cleared transaction, not an authorization, and a platform can't stop a cardholder from filing a fraud dispute. Card reversals belong to the merchant or the network and run on their clocks, while expense reversals are part of the employee relationship and fall under employment law.
B2B payments: stablecoins and blockchain payments
Most exceptions end in someone's discretion rather than a rule.
| Exception | The way back | Who starts it |
|---|---|---|
| Wrong address or typo | Only if the holder cooperates, or an issuer or custodian helps | The payer |
| Wrong chain or unsupported wallet | Sometimes a custodian recovers it for a fee; Circle says the coins are lost | The payer |
| Issuer freeze | The issuer's discretion, or a court; there's no appeal process | The issuer, often on an order |
| Depeg (the coin trades below $1) | Redeem directly if the issuer is solvent; others sell at a loss | The holder |
| Off-ramp fails to pay out | Fiat or coins returned, depending on the contract | The orchestrator |
Issuers freeze on orders and on their own judgment, and they don't freeze on request. When Drift, a crypto trading protocol, was drained in April 2026, about $232 million of the stolen USDC moved from Solana to Ethereum through Circle's own transfer protocol over about six hours, and Circle didn't freeze it. Issuers make mistakes too: on October 15, 2025 Paxos minted 300 trillion PYUSD by error and burned it about 20 minutes later.
Refunds are new payments in the other direction. The design work is in what the chain doesn't handle: an expired quote, an off-ramp that fails after the coins arrive, a frozen inbound payment, a bank-rail fallback when a chain is down.
Card issuing: launching a card program
The exceptions that cost the most in card issuing are program-level ones, and they run on long clocks.
| Exception | The way back | Clock |
|---|---|---|
| Bank under a consent order | Regulator's approval for new programs; re-verify existing cardholders; lookbacks | Months to years |
| Bank exits or doesn't renew | Migrate the BIN, reissue under a new bank, or wind down with regulatory approval | 180-365 days' notice, then months |
| Processor change | Convert at the same bank (BINs may stay) or reissue | 4-9+ months |
| Disputes and late transactions after a move | The old BIN keeps receiving them | Six months or more |
| BIN release | Only after the BIN has been inactive for at least 120 days; no disputes after release | 120+ days |
| Middleware or ledger failure | Freeze until a bank can reconcile from its own data | Months (Synapse) |
| Bank crosses $10B in assets | Reprice, or move debit to an exempt bank | By July 1 of the next year |
Two smaller reversals hit the profit and loss of every program. A refund on a debit card returns no interchange to the issuer, so the program loses its interchange on that sale. And an ATM withdrawal runs the other way: the issuer pays the ATM's bank $0.30-0.60 in interchange, plus network fees, so a "free ATMs" promise costs money on every withdrawal.
I'd want both banks' contracts to say who handles a chargeback on an old-BIN card three months after the migration.
Cloud security (CNAPP): posture, workloads and permissions
Suppressed finding
- Where
- AWS Security Hub
- Expiry
- None built in
- The catch
- Sticky; new findings for the same issue still appear
Exemption (waiver or "mitigated")
- Where
- Microsoft Defender for Cloud
- Expiry
- Optional
- The catch
- Marking a resource mitigated raises the secure score; up to 5,000 per subscription
Mute rule (static or dynamic)
- Where
- Google Security Command Center
- Expiry
- Dynamic rules can expire
- The catch
- Static rules mute future findings indefinitely
Suppression rule
- Where
- AWS GuardDuty
- Expiry
- None
- The catch
- Archived findings drop out of attack-sequence detection
Targeted risk analysis
- Where
- PCI DSS 11.3.1.1
- Expiry
- Reviewed by the assessor
- The catch
- "Addressed" can mean mitigated another way
The GuardDuty case is the one I'd teach. Its Extended Threat Detection, on by default since December 2024, correlates events over a rolling 24 hours into a single critical "attack sequence" finding, and it ignores archived findings, including ones archived by suppression rules. A rule written to cut noise can blind the engine meant to catch the attack, which is why AWS advises reviewing suppression rules.
Rules reverse as well. The SEC's SolarWinds case was dismissed with prejudice on November 20, 2025, and the members of the US Cyber Safety Review Board, which had called Storm-0558 "a cascade of security failures", were dismissed in January 2025. Snowflake moved its MFA deadline twice, from November 2025 to August and then October 2026. And the UK's data regulator cut Capita's proposed £45 million fine to £14 million.
Identity and trust: KYB, KYC and ongoing monitoring
Most of the work in this team lives in exceptions, and several of them run on someone else's clock. The restrict, review, close and report paths are where examiners look and where good customers get hurt, so it pays to design them before the happy path.
| Exception | The way back | Clock |
|---|---|---|
| Name or EIN mismatch at onboarding | Ask for documents; manual review | Days per round trip |
| Fraudulent filing on a real company's registry record | Some states can now mark or reject it; in others, a court order | Weeks to months |
| Merchant listed on MATCH | Only the acquirer that listed it can remove it | Its timeline |
| Person can't be verified (US bank rule) | Restrict the account, then close it after attempts fail; consider a suspicious activity report | Set by the bank's procedures |
| Sanctions false positive | Clear it with date of birth, nationality and address; unfreeze; apologize | Hours to days |
| Sanctions true match | Block or reject; report to OFAC within 10 business days | Unblocked only by an OFAC licence or delisting |
| 314(a) match | Answer FinCEN within two weeks; a match alone isn't a reason to close | Two weeks |
| Law enforcement "keep open" letter | Keep an account you'd otherwise close | Until the letter lapses |
| Ownership mismatch, high-risk federal company (Canada) | Report to Corporations Canada | 30 days |
| Wrongful offboarding | Reinstate; since August 2025 US exits draw scrutiny for political or reputational reasons | Weeks |
| Regulator-ordered lookback | Re-review a past period and file the reports you missed | Months, with consultants |
Lookbacks are the expensive one. The Fed's 2024 order against Evolve Bank & Trust required a review of its fintech partners' wires over six months for missed reports; the FDIC told Sutton Bank to re-run identity checks on every prepaid customer since mid-2020. If your bank gets one, your operations team does the work.
A fraudster can reinstate a dissolved company, name themselves an officer and apply to your platform, and the registry match will be perfect. The way back starts with the victim business asking the state to fix the record, which in some states needs a court.
Login and access for apps: authentication and authorization
Every reversal is also an attack path: resets, passkey removal, token revocation, unlinking accounts, disconnecting SSO, role changes, transferring an organization's ownership.
| Exception | The way back | Who starts it |
|---|---|---|
| Lost device | A backup method; synced passkeys survive, device-bound keys don't | The user |
| Locked account | A timer, email link, admin or re-verification, each a recovery path | The user or the risk engine |
| Takeover | Revoke sessions and tokens, reset, notify, review recent changes | Detection, often by an outsider |
| SSO connection fails | The last working settings or a break-glass admin | The customer's admin |
| Leaver still active | Revoke tokens and keys; transfer what they own | An audit or an incident |
Recovery is the exception every MFA rule allows, which is why attackers target it. Money follows its own rules: in the US a consumer's liability for an unauthorized transfer depends on how fast they report it ($50, $500 or unlimited), while a payment someone was tricked into sending usually counts as "authorized". In the EU, if the payer's provider skipped strong authentication, the payer isn't liable unless they acted fraudulently.
Models and inference: what AI runs on
Rate limit or spend cap hit
- Who starts it
- The provider's limiter
- Clock
- Seconds, or until the 1st of next month
- The way back
- Back off with jitter; fail over; ask for a tier increase
Model retired
- Who starts it
- The lab or cloud
- Clock
- 60 days to 6 months; 20 days seen
- The way back
- Re-test on the replacement; pin the next snapshot
Bad serving change
- Who starts it
- The provider
- Clock
- Hours to weeks to detect
- The way back
- Provider rollback (GPT-4o's sycophantic update came out about four days after release); your own evals
Price step-up
- Who starts it
- The provider
- Clock
- A dated announcement, or a promotion ending
- The way back
- Route elsewhere; renegotiate
Capacity product withdrawn
- Who starts it
- The provider
- Clock
- Immediate for new buyers
- The way back
- Existing contracts honoured; buy elsewhere
Compute deal cancelled or reshaped
- Who starts it
- Either party
- Clock
- 90 days for xAI's capacity to Anthropic; years for take-or-pay
- The way back
- Other sites, other chips
Rule reversed
- Who starts it
- A government
- Clock
- Months
- The way back
- Switchable architecture; exit rights in contracts
Reversals run both ways. OpenAI's "$1.4 trillion" of compute ambitions became about $600 billion through 2030 in reporting by February 2026, and the expansion of the Abilene site beyond 1.2 GW was dropped. Export rules went from ban to unban to a revenue share that was never codified, all within 2025.
Observability: metrics, logs and traces
| Exception | The way back | Clock |
|---|---|---|
| Data needed from the archive | Rehydrate into the index, or query in place | Minutes to hours, plus fees |
| Sampled or dropped data | None; it's gone | Never |
| Cardinality or log spike on the bill | Ask for a one-time credit; vendors sometimes grant one | A negotiation |
| Bad deploy | Roll back, the most common mitigation | Minutes |
| Alert flapping or false pages | Tune the rule or move to SLO burn rates | Weeks |
| Postmortem actions not done | Track them; Google says an unreviewed postmortem "might as well never have existed" | Next incident |
| Legal hold or security investigation | Freeze deletion | Until released |
| Forced tool migration | Move off Opsgenie (support ends April 5, 2027) or Grafana OnCall open source (archived March 24, 2026) | Months |
Rules reverse too. The US federal logging memo M-21-31 was rescinded on May 22, 2026, a federal court struck down part of HHS's guidance on tracking technologies in 2024, and the HIPAA Security Rule update has stalled. Product reversals follow public pressure: after the Storm-0558 intrusion in 2023, which agencies could only detect with logs from a premium tier, Microsoft gave standard customers more than 30 log types at no extra cost.
Phone numbers, messaging and voice
Most of this team's operational load lives in exception paths, and nearly all of them run on someone else's clock.
| Exception | The way back | Clock and cost |
|---|---|---|
| 10DLC brand fails the identity check | Resubmit exact legal data, or appeal | A few dollars per resubmit, about $10 per appeal (TCR) |
| Campaign rejected by the DCA | Fix description, samples, opt-in proof; resubmit | Days per round; providers report $10-20 per review |
| Toll-free verification rejected | Fix and resubmit | Days to weeks |
| WhatsApp template rejected or recategorized | Appeal (decided within 24 hours) or request category review within 60 days | Hours |
| WhatsApp enforcement | Appeal, answered in 24 to 48 hours; some spam violations can't be appealed | Blocks of 1 to 30 days meanwhile |
| RCS agent suspended | The carrier can reinstate; the partner can request launch again | The carrier's timeline |
| Port rejected | Fix the mismatch and supplement the existing order (a "SUP"), don't start a new one | 1 business day (simple) or 4 (non-simple) once clean |
| Port-out fraud on a mobile | Wireless carriers must authenticate port-outs, notify customers and offer a free lock (FCC rules adopted Nov 2023) | Hours matter |
| Improper SHAKEN attestation | STI-GA can revoke the provider's token | No token, no A or B attestation |
| Consumer opts out | Only the consumer can opt back in (START, UNSTOP) | FCC ceiling 10 business days; carriers expect immediate |
Regulators reverse themselves too. Brazil made the 0303 telemarketing prefix optional in August 2025, and federal prosecutors asked for it back in January 2026.
Say a dental group moves its main line to your platform, and the port form uses the practice's trading name while the losing carrier's record has the legal name. The port comes back rejected. The fix is a supplement to the same order, and a support team that doesn't know that starts over and loses days.
I'd design the rejection path before the happy path, since that's where your customer's launch slips and where they decide whether your platform earns its markup.
Voice AI: real-time voice agents
Most reversals on a call are small and happen every minute: a speculative reply is cancelled when the caller keeps talking, the agent's turn is cut back after an interruption, a failed transfer comes back to the agent. The dangerous ones are side effects. A tool call cancelled mid-flight because the caller changed their mind may already have done something, and I couldn't find how vendors handle that. An outbound dial retried after an ambiguous timeout can ring the same person twice, a second TCPA exposure.
Caller revokes consent
- Who starts it
- The caller, by any reasonable means
- Clock
- Honour within 10 business days
- The way back
- Suppress the number everywhere
Transfer fails
- Who starts it
- Trunk, carrier or an unanswered human
- Clock
- Seconds
- The way back
- Return to the agent; offer a callback
Model or price change
- Who starts it
- The vendor
- Clock
- Days to months; previews without notice
- The way back
- Pinned snapshots; regression tests with timing
Vendor shuts down after an acquisition
- Who starts it
- The acquirer
- Clock
- Weeks: PlayHT's API went dark in July 2025
- The way back
- Re-integrate; cloned voices may be lost
Deployment pulled back
- Who starts it
- The business
- Clock
- After the damage
- The way back
- Rehire, apologize, rethink scope
Commercial terms reverse too. Bland raised its per-minute price by 22-56% in December 2025, and ElevenLabs said in February 2025 that it was absorbing language model costs and would eventually pass them on.
Field Guides are learning notes, not legal or compliance advice. Rules and fees change; check the cited primary sources before you act on anything here.