ralph-cancel

To cancel an active workflow loop and clean up persisted state, the system validates the active session, writes a cancel signal file, and updates the state to inactive. This ensures proper shutdown and removes transient state.

State management cleanup for a shutdown loop is the process of deactivating an active persistence session and removing transient state files. This prevents drift between runs and ensures subsequent workflow executions start with a clean baseline.

To stop persistence and reset state for a clean subsequent run, you emit a cancel signal that deactivates the active loop and clears the persisted state files. This prevents state drift and prepares the environment for fresh execution.

Yes, you need an existing state file to cancel an active loop. The system validates the presence of the specific state configuration file before it can successfully write the cancel signal and update the active status to false.

Loop state drift occurs between runs when an active persistence loop is not properly shut down, leaving transient state files behind. Canceling the loop and cleaning up these state files prevents inconsistencies in future executions.

If the state file is missing when you try to cancel the loop, the cancellation process cannot proceed because the system validates the presence of this specific file to confirm an active loop exists before writing the cancel signal.