Run Outcomes Reference
Quick reference for customer charges and creator earnings across common run scenarios.
Audience
Buyers and creators using Edgaze.
Overview#
This table summarizes customer-visible billing outcomes for hosted runs, API runs, bundles, BYOK, failover, and payouts.
For narrative detail, follow the doc link in each row.
Reference table#
| Scenario | You pay | Creator earns | What you see | Learn more |
|---|---|---|---|---|
| Hosted run success (wallet) | Full displayed price | Under the creator fee schedule | Run completes; wallet balance drops | Run a Workflow |
| Hosted run success (bundle) | One prepaid run consumed | Under the creator fee schedule | Runs remaining count updates | Funding Runs |
| Hosted run failure | No ordinary run charge | No | Failure reason; no ordinary charge | When Runs Fail |
| Cancel before start | No | No | Cancelled before start | When Runs Fail |
| Cancel mid-run | No ordinary run charge | No | Run cancelled | When Runs Fail |
| Insufficient wallet | No | No | Insufficient funds message | Funding Runs |
| Bundle available | Bundle used first | On success only | Bundle draw indicator | Funding Runs |
| Bundle depleted | Wallet or no run | On success only | Prompt to top up wallet | Funding Runs |
| Wallet after bundle | Wallet on success | On success only | Same as wallet success | Funding Runs |
| API wallet run | Same as wallet success | On success only | API run status and charge | API Runs |
| API spend cap reached | No | No | Spend cap error | API Runs |
| BYOK run success | Displayed Edgaze price; provider bills you | Under the creator fee schedule | BYOK pricing note | BYOK |
| BYOK failure | Per the displayed BYOK terms | No | BYOK note plus error | BYOK |
| Failover enabled, success | Displayed price | On success | No visible price change | Failover |
| Failover disabled, failure | No ordinary run charge | No | Standard failure message | Failover |
| Creator changes price (new version) | Price shown for selected version | On successful runs | Per-version prices in selector | Version Pinning |
| Buyer owns pinned version | Pinned price per run | On successful runs | Version dropdown | Version Pinning |
| Version unavailable | No run charge | No | Availability error | Version Pinning |
| Nested or remixed workflow | Displayed combined price | Each creator earns separately | One price before the run | Remix and Nested Workflows |
| Refund request | Decided after case-by-case review | May be adjusted | Response from support | Refunds |
| Bundle expiry (2 years) | Expired runs cannot be used | No | Expired bundle message | Bundles Expiry and Refunds |
| Creator payout pending | None | Earnings waiting in pending | Pending on dashboard | Creator Earnings Guide |
| Creator payout available | N/A | Cleared after 7 days | Available balance | Creator Earnings Guide |
| Creator payout paid | N/A | Transferred via Stripe Connect | Payout history | Payout System |
| Demo or builder test | No | No | Demo or preview label | Run a Workflow |
| Stopped at the compute limit | Consumed compute may be retained | No | Compute-limit stop message | When Runs Fail |
| Legacy unlock listing | Legacy unlock purchase | Under purchase-time terms | Unlock versus per-run copy | Legacy Unlock |
Notable exceptions#
- Stopped at the compute limit: Already-consumed compute may be retained. Margin is released. This is separate from an ordinary failure.
- Demo and builder test: Never billed.
- Bundle expiry: Unused prepaid runs expire after two years. Creators do not earn on runs that were never used.
Related policies#
Was this useful?
Your response helps us improve the documentation.
Related documentation
Billing & Runs
How workflow runs are priced, funded, settled, and refunded. Step-by-step guides for buyers, creators, and developers.
Run a Workflow
How to open a workflow, fund a run, and what happens when it completes.
What You Pay For
How the per-run price is built, what the creator earns, and what Edgaze keeps.