If your risk management settings didn't trigger when you expected them to, work through the checks below in order — the most common causes are at the top.

You might be experiencing this if:

This is the most common reason risk management doesn't trigger.

Setting a value in the Risk Management panel is not enough on its own. Each parameter also has an enable toggle that must be switched on. If a limit shows as DISABLED, it is configured but not active — it will not trigger regardless of what the market does.

Check each parameter you expected to trigger. If it shows as DISABLED, enable it and confirm it shows as active before your next session.

Applies to Tradovate accounts only.

For Tradovate accounts, Tradecopia sends your risk parameters to Tradovate's own risk engine. If you configured or changed your parameters but did not push them, Tradovate has no record of your current settings and cannot enforce them.

This push is required every time you change any parameter — it is not automatic and does not happen in the background. If the Risk Management panel shows Never synced or a sync timestamp from before your last change, your settings have not reached Tradovate.

Push your settings from the Risk Management panel and check the sync status confirms the update before your next session. For more detail on this specific scenario, see Why aren't my Tradovate risk settings taking effect?.

Risk management sends a market close instruction the moment your threshold is reached. That close is executed by your broker at the prevailing market price.

In fast-moving markets, price can move beyond your configured threshold before the broker's close order is fully processed. This means your account may have exceeded the limit before the position was closed — not because the risk manager failed to trigger, but because broker-side execution during rapid market movement could not achieve the exact threshold price.

This is normal market behaviour. The risk manager did its job — the final exit price reflects the conditions at the broker level at the moment of execution.

If you believe a meaningful discrepancy occurred beyond normal market slippage, contact the Tradecopia support team and we can look at the specifics together.

Applies to Rithmic accounts only.

For Rithmic accounts, Tradecopia's own engine manages your risk thresholds locally. If the app was closed or lost its connection at the moment your threshold was hit, the engine was not running and could not trigger.

Check whether the app was open and connected to your broker during the relevant window. For Rithmic accounts, Tradecopia must be running and connected throughout your trading session for risk management to function.

Applies to Rithmic accounts only.

Weekly profit and loss limits are not currently supported for Rithmic accounts. If you have configured weekly parameters on a Rithmic account, they will not trigger — the parameters are visible in the UI but are not enforced on Rithmic.

Use daily profit and loss limits for Rithmic accounts. Daily limits are fully supported and will trigger correctly once enabled.

Applies to TopStepX accounts only.

Full risk management through Tradecopia is not yet available for TopStepX accounts. Parameters visible in the Risk Management panel for TopStepX accounts may not be enforced through Tradecopia's engine.

Configure your risk settings directly on the TopStepX platform. A note confirming this is also visible in the Risk Management panel when a TopStepX account is selected.

If you have worked through all the checks above and risk management still did not trigger as expected, contact the Tradecopia support team. Share which account and broker are affected, what parameter was configured, and what happened at the time the threshold should have triggered — and we can investigate from there.