Library · Payment orchestration · How to run this
Outage fail is not a dead token
Outage fails and later successes make recover %. Recover % = later successes ÷ outage fails × 100. Type both.
Pair: Retry after outage on Orchestration. Share: gateway outage share. Token: token fallback.
What you type
Outage fails — auths that failed during the gateway outage window.
Later successes — of those, retries that approved after the outage cleared.
Recover % = later successes ÷ outage fails × 100. Widen the retry window when recover % is thin — do not invent a recover chip.
What not to do
Do not invent recover %. Do not mix hard declines into outage fails. Do not treat new checkouts as later successes. Do not average every MID when one owns the hole.
Related: Orchestration, gateway outage share, token fallback, retry window.
Procedure
- Type outage fails and later successes.
- Read recover %.
- Widen the retry window when recover % is thin.
Failure modes
- Inventing recover %.
- Mixing hard declines into outage fails.
- Treating new checkouts as later successes.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- Retry-after-outage recover %
- Later successes ÷ outage fails × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this gateway outage share?
- Sibling outage book. [Gateway outage share](/manuals/spreedly-gateway-outage-share) is outage attempts ÷ total. This page is later successes ÷ those outage fails.
- Is this network token fallback?
- Related retry path. [Token fallback](/manuals/spreedly-network-token-fallback) is token fail then PAN. This page is recover % after a gateway outage.
- What recover % should I invent?
- None. Type outage fails and later successes from the same outage window.