Troubleshooting
A workflow node failed
Inspect the first failed node, exact fields, outputs, branch, connection, resource, and external status.
Automation buildersBeginnerAvailable
What this guide covers
- Later nodes cannot run normally when a required earlier node fails; diagnose the first failure.
- Prerequisites: Workflow execution context and the failing node name/type.
- Result: The node produces documented outputs and the next path runs.
- Limit: Do not assume every node automatically retries; only rely on retry behavior explicitly documented for that node or service.
What this is and when to use it
Later nodes cannot run normally when a required earlier node fails; diagnose the first failure.
| Use it when | Expected outcome |
|---|---|
An execution exists but stops or reports failure. | The node produces documented outputs and the next path runs. |
Before you begin
- Workflow execution context and the failing node name/type.
Prerequisites
Workflow execution context and the failing node name/type.
Complete the task
- Open the node's dedicated reference page.
- Compare required fields and conditional fields with the saved configuration.
- Check input variables and preceding outputs.
- Validate Sender, template, function, connected account, URL, or permissions.
- Run Test with matching data.
- Fix, save, and monitor a controlled live execution.
Confirm it worked
- The node produces documented outputs and the next path runs.
Common problems
| Symptom | What to check |
|---|---|
Test passes but live fails | Check external account, provider rules, Balance, and live-only data. |
Wrong branch follows | Inspect Condition, Classifier, or A/B output and connected handle. |
Current limitations
Do not assume every node automatically retries; only rely on retry behavior explicitly documented for that node or service.
Product boundary
Do not assume every node automatically retries; only rely on retry behavior explicitly documented for that node or service.
Where to go next
Related documentation
Workflow node referenceChoose from every node in Yanola's Triggers, Messages, Logic, AI, Integrations, and Actions palette.Workflow failures and debuggingTrace trigger matching, validation, branch decisions, node failures, variables, integrations, and usage.Variables contain unexpected valuesCheck variable scope, exact path, trigger context, execution branch, preceding node output, and value type.