How do I edit Backtest Configuration after results are generated?
After a backtest result is generated in FYERS Automate, you can modify only the slippage (%) value from the existing result. The result updates based on the revised slippage.
For any other change, such as the time period or strategy workflow, you need to run a new backtest. Each new backtest creates a new strategy version, such as V1, V2, V3, and the previous results can be viewed from Backtest History.
Editable configuration
Only slippage can be changed after a backtest result is generated.
When you update slippage, the backtest result is recalculated instantly using the modified slippage percentage. This helps you compare how expected execution price differences may affect the strategy result without creating a new backtest version.
Changes such as date range, initial capital, or workflow logic cannot be edited within the same generated result.
What if…
| Scenario | Solution |
|---|---|
| I change only the slippage | The result updates instantly with the modified slippage. |
| I want to change the time period | Run a new backtest. A new strategy version is created. |
| I change the strategy workflow | Run a new backtest. A new strategy version is created. |
| I want to view an older result | Open Backtest History to view previously run backtest results. |
Related Articles
How do I run a backtest in FYERS Automate?
You can run a backtest from the Automate workflow after the strategy is ready for testing. The backtest uses your selected date range, capital, and slippage value to simulate how the strategy would have performed using historical data. Use this ...How do I view previous backtest results in Backtest History?
Backtest History in Automate lets you view previously run backtest results for a strategy. This is useful when you want to compare earlier results, review past configurations, or check different strategy versions created after changes. Each time you ...What is Backtest in FYERS Automate?
Backtest in FYERS Automate helps you test an automation strategy using historical market data before running it live. It shows how the strategy would have performed in the past based on your selected time period, capital, slippage, and order ...Why are no trades shown in my backtest results?
If your backtest shows no matching trades found, it means the automation did not generate any trades during the selected backtest period. A backtest generates trades only when the workflow conditions are triggered during the selected historical ...Why do backtest results differ from live strategy performance?
Backtest results in FYERS Automate are based on historical market data and the inputs selected during the test, such as date range, initial capital, and slippage. Live strategy performance may differ because real orders are affected by current market ...