Scheduled tasks: runs, delivery, recovery

Open Scheduled tasks, select your demonstration task, and inspect its history. The task defines the schedule; each trigger creates a separate run.

Try it · Select the demonstration task and expand its run history.

Open a successful run and check its time, steps, and output. Execution success and delivery are separate results, so inspect the delivery records too.

Try it · Expand a successful run and its delivery records.

To stop this run, select Cancel this run. Active work first enters cancellation requested. Any files already changed are not automatically restored.

Try it · Cancel the demonstration run, then check its final state.

If a run was interrupted, confirm the old process stopped and inspect file changes and external sends. Record your review, then unlock it. The task stays paused.

Try it · After reviewing the effects, enter a note and unlock while keeping the task paused.

Retry delivery when it failed or is waiting to retry. If delivery is unknown, check the receiving side first to avoid sending a duplicate.

Try it · Compare failed and unknown deliveries and locate the available retry action.

Administrator Agent tasks can use a subscription connection and model with explicit file and web permissions. Script tasks cannot choose this engine, and unrestricted terminal access is unavailable.

Try it · Create an administrator Agent task and inspect the execution engine settings.

Run a task against demonstration documents. Read its output, then check delivery. Pause the task to stop future scheduling while keeping its history available.

Try it · Review the demonstration run, edit the task, clear Enable immediately, and save.