What if a workflow breaks?
The Builder who built it fixes it and republishes. You only pay for runs that actually work.
Written By Philippe
Last updated 3 days ago
Who's Responsible
Builders own their workflows. That means they're on the hook when something goes wrong.
This isn't a "sell and forget" marketplace. Builders have skin in the game because their reputation and revenue depend on their workflows working.
Incentive Structure:
Builder fixes workflow → Workflow works well → More runs → More revenue
Quality = Earnings correlation. The better the workflow works, the more the Builder earns.
What Happens When a Run Fails
If a workflow fails mid-execution, you don't pay the full price. The system only charges for resources actually consumed, and unused budget is refunded automatically when the run settles (~5 min). See How Billing Works for the full deposit-deduct-refund cycle with examples.
Quality Control
The marketplace tracks performance. Success rates. Run times. Error frequencies. This data is visible.
Quality Signals:
The Builder dashboard tracks every run — success rate, run time, error frequency — and Producers see these numbers on each workflow's listing. There is no marketplace status assigned from a success-rate threshold.
Workflows that consistently underperform lose Producers. A broken workflow's owner can fix it and republish. The platform may manually remove workflows that violate policy.
Evolution of the Marketplace:
- New workflows launch
- Tested by users
- Performance data emerges
- Good workflows attract more runs and revenue
- Underperforming workflows attract fewer runs and revenue
- Quality improves (self-cleaning)
Good workflows rise. Bad workflows disappear. The marketplace self-cleans over time.
Before You Buy
Every workflow shows its track record. You can see how many times it's been run, how often it succeeds, and what other Producers think.
Due Diligence Checklist:
Don't buy blind. Check the stats. Read the reviews. Test with a few runs before going heavy.
The Bottom Line
Related
Was this helpful?
Still need help? Ask the team