Failover
When Edgaze switches to a backup model, your price stays the same.
Buyers running workflows and creators configuring failover.
Overview#
When a primary model degrades, Edgaze may continue the run with an eligible alternative. Your displayed price does not increase because of failover.
Creators can disable failover. When it is off, a provider problem may cause the run to fail instead of continuing with an alternative. Ordinary failed runs are not charged.
Failover enabled#
If a provider problem is detected, the run may continue with an eligible alternative. Your displayed price does not change.
On success after failover, you pay the same displayed price as a run that did not fail over.
Failover disabled#
If the creator opted out in publish settings, a provider problem may cause the run to fail. The standard failure policy applies.
Special cases#
- Failover then failure: The standard failure policy applies.
- BYOK graphs: Your provider may bill your account separately. The displayed Edgaze pricing terms still apply.
- API and bundle paths: Same failover billing rules as UI wallet runs.
What you see in Edgaze#
- Publish settings: failover toggle for creators
- Buyer UI: no visible price change when failover occurs
- Failure with failover off: standard failure message
Related policies#
Was this useful?
Your response helps us improve the documentation.
Related documentation
How workflow runs are priced, funded, settled, and refunded. Step-by-step guides for buyers, creators, and developers.
How to open a workflow, fund a run, and what happens when it completes.
How the per-run price is built, what the creator earns, and what Edgaze keeps.