LearnChoosing a program
Prop Firm Time Limits and Inactivity Rules: What Keeps an Account Active?
An account can have unlimited time to pass and still close for inactivity. Keeping it available means meeting the deadlines and activity conditions that apply to its stage. Unlimited time to pass does not, by itself, remove an inactivity rule, a recurring trading requirement or a bill that falls due while you are away.
On this page
The useful question is more specific than "How many days do I have?" Ask what starts the clock, what action counts, whether that action restarts anything, and what happens at the boundary. A login, an open position and a qualifying profitable day are different events.
This guide explains those mechanics across CFD/FX, futures and perpetual prop programs. Named examples were checked on 30 October 2026. Both worked calendars use explicitly hypothetical rules.
Time limits and inactivity: which clock are you reading?
Start with the exact program, market, purchase cohort and account stage. A rule for an evaluation does not automatically describe its funded account, and a firm's futures rules may differ from its CFD/FX or perpetual rules.
| Clock | What it measures | What you need to establish |
|---|---|---|
| Passing deadline | Time available to complete an evaluation | Start event, final passing cutoff and whether an extension exists. Ordinary activity need not extend it. |
| Activation deadline | Time to take a required activation step | Whether it starts at purchase, account availability or official passing; whether you must trade, pay or complete another action. |
| Elapsed inactivity | Time since the applicable starting event or last qualifying activity | The initial start, the activity that restarts the clock and whether weekends count. |
| Recurring activity | Activity inside each required week, cycle or rolling window | Window boundaries, required number of days and the result that makes a day qualify. |
| Subscription renewal | When another payment becomes due | Billing date and the event that ends renewal. Trading activity is a separate question. |
A passing deadline can remain fixed while an inactivity deadline moves. A recurring requirement may need two qualifying days, so the most recent trade alone cannot tell you whether it is satisfied. And a subscription can continue during an inactive period. The billing guide explains renewal and cancellation separately.
For example, Apex's current Intraday and EOD evaluations provide 30 calendar days of access from purchase, including weekends and holidays. Its help page specifies expiry at 6:00 p.m. ET on Day 30 and provides the expiration date in the dashboard. Final-day passing requires the target and other rules to be met before the trading-session review cutoff, rather than treating the later access-expiry time as extra trading time. Apex evaluation access
Apex's separate activation page gives seven calendar days from the evaluation being officially marked Passed, not from the intraday moment the target is reached. That window still applies when the evaluation passes on its final access day. Under the activation-fee process described there, missing the window permanently ends that activation opportunity; a new evaluation must be passed. Apex PA activation
Those are different start events and different things that can expire. For the broader transition, use the evaluation-to-funded checklist; for what an activation payment buys, see activation fees.
What actually counts as activity?
Read the required event before planning around the duration. The examples below illustrate different definitions, not a ranking of how easy the accounts are to retain.
| Published example and scope | Qualifying activity and period | Stated consequence or condition |
|---|---|---|
| E8, Classic Markets and Perpetual Futures accounts | Place and close at least one trade within 60 days. The rule also covers new accounts with no trading history. | Account closure after inactivity. E8 allows a planned absence for travel if you contact support before it begins, but its page does not say how long the absence may last or whether the count pauses. E8 inactivity rule |
| Lucid, evaluation and funded accounts covered by its inactivity help page | Trading must result in at least $1 of net profit or loss within 30 calendar days. A login alone does not meet that stated condition. | The active-status policy treats the account as abandoned and permanently deletes it. The page does not explain every aggregation or cutoff detail. Lucid inactivity policy |
| Tradeify Futures, evaluation and funded accounts covered by its FAQ | At least one trade per Monday-through-Friday week, on each account. | Its evaluation answer says an account can close after an email warning; its account-management answer describes deletion after warning and no reinstatement for inactivity removals. Tradeify FAQ |
| Apex, Intraday and EOD Performance Accounts | Two trading days, each with at least $50 net profit, in the latest rolling 30 calendar days. | Too few qualifying days makes the account eligible for inactivity closure. The policy describes courtesy notices and permanent removal if closed. Apex PA inactivity |
Do not transfer E8's 60-day Classic Markets/Perpetual Futures wording to its Futures accounts. The Signature futures source disagreement is addressed below. Likewise, Tradeify Futures and Tradeify's separate CFD/FX offering are not interchangeable. Apex publishes a different policy for older Legacy accounts; the row above is scoped to Intraday and EOD PAs.
The activity definition can make an apparently recent account inactive. An open position does not satisfy a rule requiring a completed trade. A small positive result does not satisfy a larger net-profit threshold. Several qualifying trades on one day still need not provide several qualifying days. The minimum and profitable-day guide explains the counting step.
Keep the consequence equally precise. Expiry of an evaluation, loss of an activation opportunity, deletion and eligibility for closure are not interchangeable descriptions. A warning requirement is part of the rule, but it is not an extra period you can assume will always arrive in time.
Worked calendar: trading moves one deadline, not both
Consider a hypothetical evaluation with the following rules. These are invented inputs, not the rules of a named firm:
- Purchase and access start at 12:00 UTC on 3 November 2026. Passing must be completed before 12:00 UTC on 3 December, exactly 30 × 24 hours later.
- An inactivity limit starts at purchase and expires after exactly 14 × 24 hours. Completing an opened-and-closed trade restarts that interval at its closing timestamp. There is no minimum profit requirement in this model.
- Both clocks run through weekends. At either deadline, closure takes effect before an action recorded at the same timestamp could save the account. There are no warnings or extensions.
- Only the two trades listed below occur. Each opens one hour before it closes. All other account rules are assumed satisfied, and neither trade completes the passing requirements. This example calculates time limits only.
The two calculations are:
Passing deadline = purchase timestamp + 30 days
Inactivity deadline = purchase timestamp, or latest qualifying close, + 14 days
| Event, all times UTC | Inactivity deadline after the event | Passing deadline | Account position |
|---|---|---|---|
| Purchase: 3 November, 12:00 | 17 November, 12:00 | 3 December, 12:00 | Inactivity would end access first if you did nothing. |
| Trade closes: 12 November, 10:00 | 26 November, 10:00 | 3 December, 12:00 | The completed trade restarts only inactivity. |
| Trade closes: 25 November, 10:00 | 9 December, 10:00 | 3 December, 12:00 | The passing deadline is now earlier. |
| No pass by 3 December, 12:00 | The last calculated date was 9 December, 10:00 | Reached | The evaluation expires. Its valid history stops here. |
After the second trade, the account has more inactivity time than passing time. Recent activity cannot extend the fixed passing deadline. Conversely, having time left to pass would not protect it from an earlier inactivity closure.
Why a week and a rolling window need different calculations
"One trade every week" and "no more than seven days without a trade" are different rules. Under a Monday-through-Friday weekly requirement, the question is whether each specified week contains qualifying activity. Under an elapsed-time rule, the question is how long it has been since the last qualifying event. Do not replace either with "trade occasionally."
For a rolling window, make a list of qualifying dates and remove each one when it falls outside the window. The date of your oldest still-needed qualifying day can matter more than the date of your latest trade.
Here is a second hypothetical model, separate from the evaluation above. It requires two days with at least $100 of net closed profit each in the latest 30 UTC calendar dates, including the date being assessed. Results are after all trading charges, counted once. The first test is at the end of 30 October 2026; every later day is tested at day-end. Fewer than two qualifying dates at a test means immediate closure. All other rules are assumed satisfied.
The complete activity record is +$120 on 1 October, +$100 on 5 October and +$40 on 28 October. There are no other trades, open positions or adjustments. All three results are confirmed within their stated dates.
| Assessment | Dates inside the window | Qualifying days | Result |
|---|---|---|---|
| End of 30 October | 1-30 October | 1 October and 5 October | Two. The account meets this test. |
| End of 31 October | 2-31 October | 5 October only | One. The account closes at this first failed test. |
The trade on 28 October was recent, but its $40 result was below the $100 requirement. The result on 5 October qualified at exact equality. On 31 October, a Saturday, the qualifying result from 1 October leaves the window, and the count falls even though no new loss occurs. Calendar dates advance over a weekend too; that does not create an extra trading session in a closed market.
Apex's actual PA policy also uses a daily lookback, but its own session assignment and closure process control its accounts. For a new PA, it counts purchase as day one in ET. A qualifying session is assigned to its closing date, which can differ from the date a trade opened. Use those published conventions rather than this example's UTC day-end test. Apex's counting explanation
A fixed cycle works differently again: it groups activity between defined start and end dates, then begins another cycle. A rolling window advances with each assessment. If a source uses both terms, clarify whether old days age out individually, a counter resets after a particular event, or both tests operate separately.
What if the official pages give different answers?
E8 Signature provides a concrete example. The product article covers Classic Markets and Futures and gives a completed-trade interval of 60 days in both Challenge and Performance sections. The inactivity article instead states seven days for all Futures accounts. These statements were still present in E8's dedicated Futures help center when checked on 30 October 2026. Signature rules · Inactivity rules
The fact that one page is product-specific and another is rule-specific does not, on its own, establish which governs your account. Do not silently record 60 days as settled, or relabel seven days as a verified resolution.
Give support the market, program, stage, purchase date and both links. Ask which interval applies, which event starts it before the first trade, what completed activity resets it, and the exact cutoff and consequence. Keep the reply with the applicable terms. The conflicting-rules guide supplies a fuller question template and a method for deciding whether the answer actually resolves the disagreement.
An exception also needs its own conditions. E8's page allows travel once you have contacted support, but it does not say how long the absence may last or whether the inactivity count pauses meanwhile. Ask about both in the same message, and keep the reply.
Record the next deadline for your actual account
Build one record per clock, per account. Do not use the activity on one account to infer that another has met its rule.
| Field | What to record |
|---|---|
| Scope and evidence | Program, market, stage, purchase cohort, applicable document and date checked. |
| Starting event | Purchase, access made available, official passing, first trade or last qualifying close. |
| Qualifying activity | Opened or closed trade; net-result threshold; required number of distinct days; treatment of charges. |
| Time convention | Calendar or trading days, session-date assignment, timezone, daily cutoff and equality boundary. |
| Next test | Fixed deadline, last qualifying event plus interval, next weekly cutoff, or the date a needed day leaves a rolling window. |
| Reset and consequence | Exactly what restarts; any warning, exception or reinstatement process; the source's stated outcome. |
On this site, an account's "Minimum days and time limits" row gives its time limit and any inactivity rule we have recorded, with their sources. Use it as a starting point, not as a substitute for the current terms.
Use the recorded activity to calculate the next applicable test, then compare it with the passing and activation deadlines. Where a timestamp or boundary is unstated, mark that field unresolved and obtain an account-specific answer before relying on it. Calendar reminders help only when the underlying calculation is right.
Repeat the record when you pass into a new stage or change accounts. Carrying over a familiar inactivity period can be as misleading as carrying over the evaluation's loss rules.
If the required activity does not fit your intended trading schedule, address that before purchasing or before the next deadline. A trade placed only to preserve access still carries costs and loss risk. For the practical keep-or-cancel decision during a break, read Taking a Month Off: Should You Keep Your Prop Account?.
Related reading
- Minimum Trading Days and Profitable Days: establish which days count toward a requirement.
- Subscription vs. One-Time Fees: compare payment schedules and stopping decisions.
- Evaluation vs. Funded Account Rules: recheck the conditions after a stage transition.
Sources and method
Official help pages linked beside each named example were checked on 30 October 2026. They establish the stated activity conditions and consequences for their described scopes, not a universal rule across a firm's products. The E8 Signature futures disagreement remains unresolved.
The two calendars are hypothetical teaching models. Their start events, windows, exact boundaries and enforcement assumptions are stated before the calculations; dates and qualifying-day counts were independently recomputed. They are not forecasts of future firm rules, recommended trading schedules or estimates of passing or payout outcomes.