Run status

What each status means

Each chip is one of these states, quoted exactly as the app shows them:

• Up to date — the result matches your current settings and the latest data; the numbers are current.
• Running — the strategy is computing now. Inside a results view this appears as Computing with a live progress percentage (Computing results… {progress}%); you do not need to refresh, the results replace it when done.
• Out of date — a setting changed since the last run, so what you see is the previous result. The banner reads Out of date — showing last run · re-run to update, and the stale numbers are dimmed.
• Not run — the strategy has never been backtested, so there is nothing to show yet.
• Failed — the last run did not finish; use Re-run to regenerate it. One cause is a simulation left with no valid state to continue from — see bankruptcy rules.
• Unavailable — the engine cannot serve a result right now (for example while it is refreshing); the last available numbers may still be shown.

A green, up-to-date chip means the last result is current — it is not a promise that the results page will render, and a "no results" placeholder does not always mean you simply haven't run the strategy.

Why it flips to Out of date

Editing any setting that feeds the backtest flips the status to Out of date, because the saved result no longer matches your configuration. Changing the rebalance frequency, the benchmark, or a cost or tax rate in Settings all invalidate the last run. Flipping one of the three simulation assumption toggles does not: every combination is computed in the same run, so a toggle only picks which finished result is displayed. When a setting does invalidate the run, the app shows Settings changed — re-run to update the results. and keeps displaying the previous numbers, dimmed, until you re-run. A manual Save & Run is today's reliable way to bring a strategy back Up to date.

Worked example

A strategy is Up to date, rebalancing every three months. You open its settings and change the rebalance frequency to monthly, then save. Because the saved result was computed for the old cadence, the chip immediately flips to Out of date — showing last run · re-run to update and the metrics dim. You press Re-run: the chip becomes Running, the results view shows Computing results… 40%, and when the engine finishes it settles back to Up to date with the new monthly-rebalance numbers.