Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Locking a Forecast Version

After running a forecast and reviewing the results, lock the run to make it the version's official baseline.

How to lock:
  • After a successful run (status "Ready"), the Lock toggle in the upper-right toolbar becomes active
  • Click it — the completed run is designated as the version's official (canonical) baseline
What locking does:
  • Marks that specific run as the version's baseline — the numbers charts, tables, and analytics read
  • Enables overlays: overlays can only run against a locked baseline
  • Enables export: exporting requires a locked baseline
  • Prevents re-running while locked — the baseline stays stable for the work built on top of it

To re-run a locked version, unlock it first (the same toggle). Unlocking clears the official-baseline designation — overlays that referenced it will need the new run locked before they can run again.

Lock vs. Run — the key distinction:
  • Run = compute forecast numbers (repeatable while unlocked)
  • Lock = designate a completed run as the official baseline (reversible via unlock)

Lock or unlock through the assistant

In Agent mode, ask to lock a specific completed baseline or to unlock a named version. The assistant discovers the exact run and presents Allow/Deny; the server refuses an unsuccessful run or one belonging to another version. Choosing a different baseline rebases layers and clears incompatible layer locks, which the confirmation discloses. Unlocking clears the baseline selection without cancelling jobs or clearing layer locks. A later run is a separate action.