Library · Payment orchestration · How to run this
Route p95 is not workflow timeout
When p95 exceeds timeout, (p95 − timeout) ÷ timeout make over-threshold %. Type both.
Pair: Route latency p95 on Orchestration. Timeouts: workflow timeout cost. Fallback: fallback gateway share.
What you type
p95 route ms — 95th-percentile route latency in milliseconds.
Timeout ms — written route timeout in that same window.
Over-threshold % = max(0, (p95 − timeout) ÷ timeout × 100). Retune route hops when over-threshold % is fat — do not invent a latency chip.
What not to do
Do not invent over-threshold %. Do not mix workflow timeout counts into ms. Do not treat fallback share as p95. Do not average every workflow when one owns the lag.
Related: Orchestration, workflow timeout cost, fallback gateway share, condition miss rate.
Procedure
- Type p95 route ms and timeout ms.
- Read over-threshold %.
- Retune route hops when over-threshold % is material.
Failure modes
- Inventing over-threshold %.
- Mixing workflow timeout counts into ms.
- Treating fallback share as p95.
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
- Route over-threshold %
- When p95 exceeds timeout: (p95 − timeout) ÷ timeout × 100; else 0.
Work with us — We run this job on your accounts. Services
FAQ
- Is this workflow timeout cost?
- Sibling Primer clock. [Workflow timeout cost](/manuals/primer-workflow-timeout-cost) prices abandoned auths × AOV. This page is how far p95 exceeds timeout ms.
- Is this fallback gateway share?
- Related routing grain. [Fallback gateway share](/manuals/primer-fallback-gateway-share) is fallback volume. This page is route latency p95 vs timeout.
- What over-threshold % should I invent?
- None. Type p95 route ms and timeout ms from the same Primer window.