Validation checks whether the automation has the required configuration and whether its workflow can be used as defined. FIA can explain validation issues and help you work through the affected part of the automation.
Validation should be completed before backtesting and deployment.
FIA can briefly explain the relevant workflow logic when presenting a validation issue, making it easier to understand why the configuration needs to be changed.
When a validation error is being reviewed, Fix with FIA can send the relevant error context to FIA.
FIA can then:
After making the correction, validate the automation again.
No.
Required configuration must be complete.
For example, an automation requires a valid trigger. If a required trigger setting is missing or incorrect, the issue must be fixed before the workflow can be treated as valid.
No.
Validation checks whether the automation is configured correctly.
Backtesting applies the strategy logic to historical data so you can review how those rules would have behaved over the selected historical period.
A valid automation should still be backtested before deployment.
| Scenario | What to do |
|---|---|
| What if I built the automation manually? | You can still switch to Use FIA and ask FIA to validate the workflow on the canvas. |
| What if there are several validation errors? | Review and correct the affected configurations, then run validation again. |
| What if validation succeeds but the strategy is not what I intended? | Validation does not replace your review of the trading rules. Check the trigger, conditions, quantities, actions, timing, and exits before backtesting or deploying. |
| What if I fix the workflow after a backtest? | Backtest the revised version again so the historical test corresponds to the strategy you are considering for deployment. |
Last updated: 26 Aug 2026