Exporting a Forecast Version

Export takes a forecast version's numbers out of Galdera: as CSV files you download, as a publication to the consumer-facing tables that downstream integrations read, or both. It is a separate step from locking: locking designates the official baseline inside Galdera; exporting is how that locked set leaves.

• The version's locked baseline run
• Every overlay on the version that is locked and whose run was computed against that same locked baseline. An overlay locked against an older baseline is not part of the current locked set and is skipped.

• Open the version and choose Export from the toolbar's overflow menu (the item reads "Exporting…" while in progress)
• Export requires a locked baseline — with nothing locked, the export is rejected
• The dialog offers two things, and you can pick either or both. Download CSV files gives you the numbers as files you download from the dialog. Publish to warehouse writes the locked forecast to your export tables, where downstream integrations pick it up. Pick at least one
• The forecast window applies to the CSV files only. It defaults to the version's full horizon; narrow it if you only need part of the forecast
• Progress shows in the dialog while the export runs. Closing the dialog does not stop the run
• When it finishes, the dialog confirms the warehouse publication and, if you asked for files, lists one download per source plus Download all for everything in one zip
• If the export fails, the dialog says why and offers Retry export, which re-runs the same request
• The dialog's address changes while it is open, so that link — or a reload — reopens the same export and its downloads
• The files for a completed export stay available for 30 days after the export runs. Nothing extends that. Reopening the dialog, downloading a file, and re-requesting the same export all reuse the files already there. Export again after 30 days and you get fresh files with a fresh 30 days
• Exported runs are marked in the version's run history

Export does not freeze the version. You can unlock, re-run, re-lock, and export again — an export always reflects the locked set at the moment you trigger it. If you move locks after exporting, the published data lags behind until you export again.