
Your Funded Account Agreement's Inactivity Clause: How Many Consecutive No-Trade Days an Automated Bot Can Safely Sit Idle Before a Firm Flags the Account
The Clause Nobody Reads Until a Bot Goes Quiet
Every funded account agreement has an inactivity clause, and almost nobody reads it closely until the question actually comes up: the bot hasn't opened a position in a while, the market's been flat, or you turned a strategy off to wait out a news week — does the firm care? The honest answer is yes, and the threshold is usually tighter than traders assume. Apex, Lucid, BluSky, and TakeProfit each define a maximum number of consecutive calendar or trading days an account can go without a trade before it gets flagged for review or, in some cases, closed outright.
This matters more for an automated account than a manual one. A discretionary trader who steps away for a week knows they stepped away. A bot that's sitting idle because a strategy's entry conditions simply haven't triggered can go quiet for the exact same stretch without anyone noticing, because nothing looks wrong — there's no error, no disconnect, just an account that hasn't traded.
Why Firms Enforce This at All
Prop firms aren't policing inactivity to be difficult. A funded account that never trades isn't generating the activity the firm's business model depends on, and an account that sits dormant for months is also the profile of someone who passed an evaluation and then abandoned it — which is exactly the behavior inactivity clauses exist to flag. The rule isn't really aimed at traders who are actively running a strategy that happens to be quiet; it's aimed at accounts nobody is managing anymore. The problem is the rule can't always tell the difference, which is why a PBT bot sitting idle for the wrong reason is worth catching before the firm catches it first.
What Actually Counts as a No-Trade Day
This is where the fine print matters more than the headline number. Some firms count a trading day as "no activity" only if zero orders were placed — a bot that places an order that gets rejected or cancelled may or may not satisfy the requirement, depending on the firm. Others require a trade to be held open across a session, not just placed and flattened in the same minute. A few only enforce the clause after the evaluation is passed and the account is funded, not during the evaluation itself. None of this is guesswork you should do from memory — the number and its exact definition live in the agreement you accepted when the account was activated, and it's worth rereading rather than assuming it matches what a different firm requires.
How This Actually Happens to an Automated Account
- A strategy's setup conditions go quiet. ORB and NR7 both depend on specific range or volatility conditions. A stretch of unusually calm, low-range sessions can mean legitimately zero qualifying setups for days at a time.
- A bot gets turned off and forgotten. Pausing a strategy during a news week or a platform update is good practice on its own — turning bots off around earnings season or index rebalancing is a real recommendation — but a bot that gets switched off and never switched back on is the single most common way an automated account drifts into inactivity.
- A single-bot account has no backup. An account running one strategy has no fallback if that strategy's conditions dry up for a week. A small starter portfolio of two or three uncorrelated bots is less likely to go fully silent at the same time, since different strategies tend to find setups in different conditions.
Keeping an Account Active on Purpose
The fix isn't forcing a trade you don't have a setup for — that's how inactivity risk turns into drawdown risk, which is worse. It's building a habit of checking account activity the same way you'd check a bot's performance numbers: know your firm's exact threshold, calendar it, and treat an approaching inactivity window as a trigger to look at why a bot has gone quiet rather than a reason to force an entry. If the answer is "the market hasn't given this strategy a setup," that's a portfolio-construction problem to fix with a second bot, not a reason to override a system that's correctly sitting on its hands.
Before you walk away from a funded account for any stretch of time — a vacation, a platform migration, a strategy pause — check the agreement's actual inactivity language first. The number is firm-specific, it's usually shorter than people expect, and it's one of the few rules in a funded account that can end an evaluation for doing nothing wrong at all.



