Handling Errors in Workflows
Flux provides several mechanisms to handle errors gracefully during workflow execution.
Step-Level Errors
If an agent step encounters an error — such as a tool failure or an unrecoverable LLM issue — the step is marked as failed and the workflow run captures the error details. You can review error logs in the run history for each workflow.
Approval Gates
For high-stakes steps, enable requires_approval to pause execution and wait for human review before proceeding. This is especially useful for action steps like sending emails, where you want a human to verify the content before it goes out.
Retry Strategies
When a step fails, you can re-run the workflow from the failed step rather than starting over. Flux preserves the outputs of previously completed steps, so only the failed step and subsequent ones need to re-execute.
Best Practices
- Use approval gates for any step that has external side effects (sending emails, making API calls, writing to databases)
- Check output schemas to ensure agents produce the data format downstream steps expect
- Test incrementally — run your workflow one step at a time during development to catch issues early
- Review tool permissions — ensure agents only have the tools they need to minimize unexpected behavior