Activepieces Flow Shows Success but Step Failed
Workaround available Cloud, self-hosted Updated November 14, 2026Based on 3 user reportsHow we research
Quick answer
A run is marked Succeeded when a step has Continue on Fail enabled, because the error becomes the step output. Inspect run details and branch on the output.
Most likely fix: Check the run detail
How to fix it
Try these in order — the most common fix is first.
1. Check the run detail
- Open the run
- Look for steps marked failed but continued
Did this fix it?2. Disable Continue on Fail where not needed
- Open the step settings
- Turn off Continue on Fail
- Enable auto retry for flaky steps
Did this fix it?3. Add a branch on the output
- Add a Router after the step
- Check for an error field
- Send a notification yourself
Did this fix it?
Symptoms
Run status is green but data is missing or a step shows failed but continued.
Why it happens
- Continue on Fail enabled
- No alert because the run did not fail
- Code-step errors treated as success
This guide also covers
- activepieces flow successful but failed
- activepieces continue on fail
Still not working?
If Activepieces keeps failing, you're not alone. See every Activepieces problem users report or the alternatives people switch to.
Done fighting Activepieces? Our small team builds your own Activepieces alternative, or any software you need: web, mobile, games, desktop. Price agreed together.
Talk to usOther Activepieces errors
- Activepieces Webhook Not Triggering
- Activepieces Runs Stuck in Queued
- Activepieces EXECUTION_TIMEOUT Error
- Activepieces Code Step Out of Memory
- Activepieces Self-Hosted Docker Not Working
- Activepieces Upgrade Broke Flows
- Activepieces Connection Expired or Authorization Failed
- Activepieces Flow Won't Turn On or Stops Running