No. FIA builds the automation from the strategy you describe, but deployment is a separate step that you control.
After FIA builds the workflow:
FIA creating or changing the workflow does not by itself deploy that strategy.
Deployment is the point at which you decide to use the automation on your FYERS account.
Keeping deployment separate means you can build, review, change, validate, and backtest the strategy before deciding whether it should run.
No.
Backtesting evaluates the strategy rules using historical market data.
Deployment runs the configured automation on your live FYERS account. Automate is not a simulated trading environment when deployed.
If the deployed workflow contains order actions, those actions can be reached when the configured triggers and conditions are satisfied.
No.
Backtesting shows how the defined rules behaved on historical data. Historical results do not guarantee future trading results.
| Scenario | What to do |
|---|---|
| What if I only want to build the automation now? | You can keep working on the workflow without deploying it. |
| What if I change the strategy after backtesting? | Backtest the revised version again before deciding whether to deploy it. |
| What if FIA builds a strategy but I find an incorrect quantity or exit? | Correct the workflow before deployment and run validation and backtesting again. |
| What if I do not want the strategy to trade on my live account? | Do not deploy it. Building and backtesting do not require you to proceed to live deployment. |
Last updated: 26 Aug 2026