Library · Payment orchestration · How to run this
A condition miss is not a timeout
Condition misses on routes make miss %. Miss % = misses ÷ routes × 100. Type both.
Pair: Condition miss rate on Orchestration. Timeout: workflow timeout cost. Fallback: fallback gateway share.
What you type
Misses — routes that missed a written condition / branch in the window.
Routes — total workflow routes in that same window.
Miss % = misses ÷ routes × 100. Fix conditions when miss % is fat — do not invent a miss chip.
What not to do
Do not invent miss %. Do not mix timeouts into condition misses. Do not treat gateway declines as condition misses. Do not average every workflow when one owns the hole.
Related: Orchestration, workflow timeout cost, fallback gateway share, failover auth count.
Procedure
- Type condition misses and routes.
- Read miss %.
- Fix conditions when miss % is material.
Failure modes
- Inventing miss %.
- Mixing timeouts into condition misses.
- Treating gateway declines as condition misses.
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
- Condition miss %
- Workflow condition misses ÷ routes × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this workflow timeout cost?
- Sibling workflow pain. [Workflow timeout cost](/manuals/primer-workflow-timeout-cost) prices timed-out routes. This page is condition misses ÷ routes.
- Is this fallback gateway share?
- Related routing. [Fallback gateway share](/manuals/primer-fallback-gateway-share) is volume on fallback. This page is condition-miss share of routes.
- What miss % should I invent?
- None. Type condition misses and total workflow routes from the same window.