When Runs Fail
What you pay when a run fails, is cancelled, or is stopped for exceeding its compute limit.
Buyers and creators using Edgaze.
Overview#
Ordinary failed and cancelled runs are not charged, and bundle runs are not consumed.
There is one separately labeled outcome: a run stopped at the compute limit, where already-consumed compute may be retained.
| Case | Buyer charged | Creator earns |
|---|---|---|
| Hosted run failure | No margin charge | No |
| User cancels mid-run | No margin; failure compute policy | No |
Failed runs#
When a workflow fails during execution, you are not charged for an ordinary failed run. The creator earns nothing. If you were using a bundle, that run is not consumed.
Cancelled runs#
Before start. If you cancel before the run fully starts, there is no charge and no bundle consumption.
Mid-run. Cancelling during execution follows the same billing as failure. There is no ordinary run charge, and a bundle run is not consumed.
Stopped at the compute limit#
When a run exceeds its compute limit, it is stopped. Charges for work already completed may remain on your wallet, as shown before the run and in wallet history.
This is shown separately from an ordinary failed run so you can identify the charge in wallet history.
Blocked before start#
Oversized input. Input above the workflow envelope is rejected before any charge or reservation. Same outcome as insufficient funds: no run, no charge.
Insufficient funds. If your wallet and bundle cannot cover the price, the run never starts.
Failover disabled. If the creator turned off model failover and the primary model fails, the run fails with no margin charge. See Failover.
Special cases#
- Demo or builder test: No charges regardless of outcome.
- API path: Same rules as the product UI.
- Nested remix child failure: Child margin is not charged. Root billing follows the same composed-run rules.
What you see in Edgaze#
- Failure: error reason and no ordinary run charge
- Cancel: cancelled state with before-start or mid-run copy
- Compute limit: explicit stop message and any applicable charge in wallet history
- Run history: final status and reason
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.