A stale-price ⚠ means a position is being valued at a close more than a week old. The math is fine, but the inputs are dated, so values and drift are only as current as that last download.
The usual fixes, in order
- Update Prices (top bar, or the value chart's button) downloads the missing recent days for every ticker. This is almost always the whole fix. The Overview's Needs attention row offers the same action when one or more held market tickers are stale.
- Check the ticker's price source. If one ticker stays stale while the rest update, its source may not cover it. Pin it to the other source on Securities & prices (see price sources).
- Rebuild history (value chart) clears and re-downloads full history. The remedy for wrong data rather than missing days; it's deliberately slow because downloads are rate-limited. It replaces only what a source can hand back: your manual and detected splits, and any price you typed yourself on a holdings snapshot, are kept. For a date the download covers, the downloaded close wins.
What is never flagged
Cash-like holdings, including money-market funds and the cash ticker, are stamped at $1 locally rather than downloaded, so an old stamp date there is normal, not a broken feed. Skip-download tickers (a fund held under a CUSIP, a delisted symbol) aren't downloaded at all: they carry no price dates and are valued from their own transactions.
A sample portfolio is judged on its own calendar. While one is open, a close counts as a week old against the sample's newest close, not today's date, so a demo household whose prices end months ago does not open on a row of stale warnings. If you update a sample's prices, its calendar moves with them. Your own portfolio is always judged against today.
An unknown price date is not called stale. The Overview will name a missing price-source setup when it can prove that configuration is incomplete, but it will not turn a transaction-price fallback into an unreliable freshness claim.
"Unusable rows were skipped"
A download can succeed and still send days with no real close (a blank or zero price). Those aren't stored because a zero would chart as a crash. The update says how many were skipped, per ticker. The effect is a small hole in that ticker's history: the chart draws straight across it, so it reads as a flat, quiet stretch rather than missing data. A Rebuild history for that ticker is the fix if the source has since published the missing days.
"Moved by a 2:1 step since the last update"
Each update re-downloads the last month of prices it already has. If a source now gives every one of a ticker's old days at half (or a third, or ten times) the price it gave before, the ticker has split. The app needs that split recorded before it stores the new prices; otherwise the older prices it keeps would sit on the wrong side of the split for good. A single odd price on one day is not a split and is simply corrected.
For tickers you hold, by transactions or statements, the update already fetches their splits. For any other ticker, such as a Screener fund or a model-library fund, the update asks for that ticker's splits only when its prices make this jump. It asks about at most ten such tickers per update, so it stays inside the source's request limits. If the source reports a split that explains the jump, the prices are saved with it. If it reports none, the update downloads that fund's whole price history again instead, so no jump is left in it.
Otherwise the update does not save the ticker's new prices, and its status line (the top bar, the Screener or the account setup, whichever you used) says why:
- checked in a later update: this update had already asked about ten tickers. Run another update.
- could not be fetched or could not be downloaded again: the request failed. The next update tries again.
- no split recorded or reported explains it: a ticker you hold jumped, and its split is not in the source's list yet. Sources often catch up within a day, so run the next update first. If the line is still there, rebuild that ticker's price history on Securities & prices.
"The downloaded history now starts on …"
A rebuild replaces the prices a source can send. If the source's history for a ticker begins later than the stored history did, the earlier downloaded days are removed. This is common after you switch a fund to another price source that has a shorter record. Positions held before the new first day are then valued at their trade prices. The status line names the ticker, both dates and how many days went. To get them back, switch the ticker to its previous source and rebuild again. Prices you typed yourself are never removed.
A price that looks wrong by a large, suspiciously round factor after a refresh usually isn't staleness. It is a missed split.