Cash Reserve checks its position every 30 minutes during market hours, but only trades when it needs to. Here's what governs that.
The 10% drift rule
On each run the system compares what you hold in the reserve ETF against the target. If the gap is more than 10% of the target, it rebalances. If not, it holds and records the run as skipped.
An example. Your target is $34,400 in SGOV and you currently hold $34,400. The drift is zero, so it holds. If you held nothing, the drift would be 100% and it would buy whole shares toward the target.
The band exists so ordinary price movement doesn't generate constant small trades.
First buy after deploy
A newly deployed Cash Reserve waits until the next trading day before it places a buy. That gives your other active systems a chance to claim their cash first. Sells are never deferred by this wait.
Existing SGOV or BOXX shares are still adopted on deploy. The wait only delays new purchases.
Same-day trim when another system needs cash
When another active system on the same account claims more cash (you deploy it, activate it, or raise its allocation), Cash Reserve recalculates its target and can sell excess reserve shares the same day.
That trim can run even if a normal cooldown would otherwise hold the system back. The daily trade cap still applies.
If you lower a sibling's allocation, Cash Reserve updates its stored target and picks up the freed cash on a later regular run. If you pause a sibling, Cash Reserve updates its target right away. Cash backing that system's open option trades stays reserved, and the rest is picked up on a later regular run.
When the brokerage cash figure lags
Some brokerages take time to reflect fills in the cash balance Cash Reserve reads. When that happens, the system can hold the position rather than selling shares it just bought, or buying again against cash that is still catching up. Execution history may note that the ETF is held while the broker's cash balance catches up with today's orders.
When your brokerage reports equity buying power separately (for example deposits that have not cleared), Cash Reserve also caps buys to that spendable amount so it does not place an order the account cannot fund yet.
Why you'll see "skipped" a lot
A skipped run in your execution history is the normal, healthy state. It means the position was checked and found to be about right.
Runs are also skipped when the account is disconnected, the system is disabled, the reserve ETF couldn't be priced, or a new Cash Reserve is still waiting for its first buy day. If skips concern you, the execution history records the reason for each one. You can use the Submitted filter on execution history to hide skips and focus on orders that were sent.
If you already own SGOV or BOXX
When you first deploy Cash Reserve, the system reads your brokerage account and adopts any matching reserve ETF you already hold into its own records, using your actual cost basis where your brokerage reports it.
You'll see an entry marked Adopted existing position in your activity feed.
This matters because it means the system won't buy a full target on top of shares you already own. Your existing holding counts toward the target.
If you buy or sell the reserve ETF yourself
That's fine. Before every rebalance, the system re-reads your live position from your brokerage and updates its own records to match.
Buy 50 shares yourself and the system notices, folds them into its records, and counts them toward the target rather than buying them again. Sell some and it adjusts down. Your brokerage is always treated as the source of truth on share count.
If your brokerage can't be reached
The run is skipped entirely. No reconciliation, no trade.
This is a deliberate safeguard. A failed read is never interpreted as you holding zero shares, because that would cause the system to buy a full position on top of what you already own. A holding is only treated as empty when your brokerage explicitly confirms it.
How fills are confirmed
An accepted order isn't treated as a completed one. The system polls your brokerage until the fill is confirmed, then records it at the actual fill price.
If an order is still working when the check window ends, it's recorded as working and reconciled on the next run. This is why an order can appear before it shows in your position.
If the brokerage does not confirm whether an order was accepted in time, Cash Reserve records that and holds new orders until the next trading day so the same trade is not placed twice.
Common questions
Why hasn't it bought anything? Most likely you're within the 10% band, cash reserved for another active system's allocation has reduced your allocatable base, equity buying power is too low for a whole-share buy, or a newly deployed Cash Reserve is still waiting for the next trading day. Check the execution history for the recorded reason.
Why did it sell? Your target dropped below your holding. That usually happens because your allocatable base fell, or another system claimed more cash (including a same-day trim after you raised a sibling allocation).
