sleep

To pause an automation workflow without losing state, you need a reversible suspension mechanism that preserves data. This approach defines sleep configuration and a state-preservation checklist to prevent data loss during maintenance.

A wake condition is the predefined criteria that resume a suspended process. It works by using timers, manual triggers, or system events to automatically restart operations after a maintenance window or cooldown period ends.

Yes, you need HA_URL and HA_TOKEN to configure a maintenance sleep window. These prerequisites, along with curl on your PATH, are enforced to ensure the system can authenticate and execute the suspension securely.

The best way to gracefully suspend a system for maintenance cooldowns is to use a reversible suspension plan. This method guarantees state preservation by defining what stops, what resumes, and how wake conditions trigger recovery.

Use a reversible sleep suspension instead of stopping a process directly when you need guaranteed state preservation. This approach avoids data loss during non-disruptive pauses and maintains automation hygiene by defining specific wake criteria for recovery.