Bot stopped trading after hitting the daily limit

Causes, most likely first

1. The daily loss limit was reached

Once the day's realised loss crosses the configured threshold, scanning halts until the next server day. This is deliberate: the day after a run of losses is when discretionary judgement is worst and when a system is most likely to be over-ridden by its operator.

2. The daily profit limit was reached

A profit lockdown exists for the same reason in the opposite direction — it stops a good day being given back. It surprises people more, because stopping while winning feels wrong, but the rule is symmetric on purpose.

3. It reset at server midnight, not local midnight

The lockdown resets on the broker's clock. If your local day starts several hours before or after the server's, the bot will appear to resume at an odd hour. See server time vs local time.

4. A loss-streak pause is active instead

This is a shorter, separate mechanism — a brief global pause after several consecutive losses, measured across all symbols rather than one. It expires on its own after a set period rather than at midnight.

Why this happens

A daily lockdown is one of the few risk controls that cannot be argued with in the moment, which is precisely its value. The temptation to trade back a loss is strongest immediately after taking it.

For prop firm accounts this control maps directly onto the firm's daily drawdown rule, and it should be set below the firm's limit rather than equal to it — equal leaves no room for slippage on the trade that reaches it.

If the lockdown triggers most days, the limit is too tight for the strategy's normal variance rather than the strategy being broken. Size the limit against a typical losing day, not against a comfortable one.