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. The creator earns nothing, Edgaze absorbs the compute used, wallet reservations are released, 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 | Edgaze absorbs |
|---|---|---|---|
| Hosted run failure | No margin charge | No | Yes: raw compute |
| User cancels mid-run | No margin; failure compute policy | No | Yes |
Failed runs#
When a workflow fails during execution, you are not charged the creator's margin. The creator earns nothing. Edgaze absorbs compute burned during the attempt. 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. Margin is not charged. Compute already used is absorbed by Edgaze. Bundle reservations are released without consumption.
Stopped at the compute limit#
When a run exceeds its compute ceiling, it is stopped. Partial compute charges from work already done may remain on your wallet. The creator's margin is not charged.
This is not presented as an ordinary failed run. You may see consumed-compute charges in wallet history without a matching margin charge.
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, no margin charge in wallet history
- Cancel: cancelled state with before-start or mid-run copy
- Killed: explicit killed message; wallet may show compute charges without a margin charge
- 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.