Skip to article
ecomservices.io
Payment orchestration · How to run this
RoutingCalculatorCascadeCalculatorRetriesCalculator3DS placementCalculatorDeclinesCalculatorAffinityNot on this page yetOptimisationCalculator

Library · Payment orchestration · How to run this

Workflow timeouts burn order dollars

How to run thisPayment orchestration3 steps
CalculatorWorkflow timeout cost · Calculator lives in the articleOpen

A workflow can time out before the auth returns. You lose the order and often still pay a retry. Lost $ = timeouts × AOV + timeouts × retry fee. Type timeouts, AOV $, and retry fee $.

Pair: Workflow timeout cost on Orchestration. Fees: retry cost waterfall. Hops: failover auth count.

What you type

Timeouts — workflows that hit the timeout before auth completed (typed from the orchestrator).

AOV $ — average order value for those checkouts.

Retry fee $ — fee billed when the timeout triggers a retry (invoice / schedule line; type 0 if none).

Lost revenue = timeouts × AOV. Retry fees = timeouts × fee. Total lost = both. Raise the timeout or cut slow hops — do not invent a timeout chip.

What not to do

Do not invent a timeout percent. Do not mix soft declines into timeout count. Do not ignore retry fee because AOV looks big. Do not treat failover hop count as the same as a timed-out workflow.

Related: Orchestration, retry cost waterfall, failover auth count, cascade pollution.

Procedure

  1. Type timeout count from the orchestrator export.
  2. Type AOV $ and retry fee $.
  3. Raise the timeout or cut slow hops when lost $ is material.

Failure modes

  • Inventing a timeout percent.
  • Mixing soft declines into timeout count.
  • Ignoring retry fee because AOV looks big.

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

Workflow timeout lost $
Timeouts × AOV plus timeouts × retry fee when the workflow dies before auth completes.

Work with us — We run this job on your accounts. Services

FAQ

Is this retry cost waterfall?
Related fee. [Retry cost waterfall](/manuals/solidgate-retry-cost-waterfall) is attempts × fee ÷ approvals. This page is workflows that timed out before auth finished.
Is this failover auth count?
Related count. [Failover auth count](/manuals/failover-auth-count) is hops per order. This page prices timeout count × AOV plus retry fee.
What timeout rate should I invent?
None. Type timeout count from the orchestrator export for the window.