productionos-productionos-pause

To pause a pipeline, invoke the productionos pause command to save the current workflow state to a checkpoint file at .productionos/CHECKPOINT.json. This preserves all active context for interrupted runs across repositories, targets, or tasks.

A pipeline checkpoint is a saved snapshot of your active workflow context stored in a JSON artifact. You need it when an interrupted run occurs across repositories or tasks, allowing you to pause execution without losing progress.

You resume an interrupted workflow by restoring from the checkpoint artifact located at .productionos/CHECKPOINT.json. The Codex-native wrapper reads the saved state to seamlessly continue the paused pipeline execution.

Yes, the pause command is applicable to interrupted workflows across repositories, targets, or tasks. It captures the active context into a single checkpoint artifact to ensure seamless pause and resume operations.

You prepare for safe restartable pauses by running the pause command, which wraps the source ProductionOS command behavior in Codex-native execution. This creates a checkpoint artifact that preserves active context for later restoration.

The checkpoint mechanism saves state specifically to .productionos/CHECKPOINT.json. If multiple pipelines run concurrently, they will overwrite this single artifact, so you should not use this approach for parallel workflow pauses.