Sleep

To delay task execution, you can use a sleep command to pause workflows for a specified duration and optionally trigger a follow-up action. This enables timed orchestration by validating duration formats like seconds, minutes, hours, or days before running the next step.

Delayed script execution supports duration formats in seconds, minutes, hours, and days. The sleep mechanism parses and validates these formats to ensure workflows pause for the exact specified timing before proceeding.

Yes, you can schedule a follow-up command or skill to run after a specified delay. By appending the follow-up prompt to the sleep instruction, the workflow automatically triggers the next action when the timer completes.

The best way to orchestrate timed reminders and staged actions is using a sleep function to defer execution. This reduces manual waiting by pausing the automation script for a set duration and then automatically triggering the next scheduled task.

To pause a workflow for one hour and then execute a review script, you can specify the delay duration and the follow-up command together, such as setting a 1h delay followed by the review skill trigger.

Sleep is designed for delaying execution and triggering follow-up actions within workflows, but it requires valid duration formats (seconds, minutes, hours, days). Complex timed orchestration may need careful validation of duration inputs to avoid workflow timing errors.