FIA can explain the automation currently loaded on the canvas, including what starts it, what rules are checked, and what actions follow. You can ask about the entire workflow or focus on one part of it.
This is useful when reviewing a strategy before backtesting or when working with an automation you did not build from scratch.
Examples include:
FIA uses the current canvas as context when explaining the workflow.
What starts the workflow or causes a particular rule to be evaluated.
What must be true before the automation continues through a particular path.
What the automation is configured to do after the required trigger and conditions are satisfied.
How different nodes are connected and what causes the workflow to follow one path rather than another.
What a particular configured node does and, where applicable, when it is evaluated.
Use Explain nodes when you want to understand the Automate building blocks themselves rather than one specific strategy.
For larger sets of nodes, FIA can present explanations in batches rather than displaying everything at once.
When working with a pre-built automation, an Explain this automation option can also provide context for the loaded workflow.
No.
Asking FIA to explain the existing logic does not itself change the canvas. A workflow change occurs only when you ask FIA to modify the automation or make an edit directly.
| Scenario | What to do |
|---|---|
| What if I only want to understand one trigger? | Ask what that specific trigger does and when it is configured to run. |
| What if I cannot understand why two nodes are connected? | Ask FIA what information or condition causes the workflow to move between those nodes. |
| What if the explanation shows that the strategy is not what I intended? | Describe the required change to FIA, then validate and backtest the revised workflow. |
Last updated: 26 Aug 2026