> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cohesive.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage Automations

> Inspect runs, change instructions, pause schedules, and recover from failed work.

Open an Automation from the left rail to inspect its instructions, schedule, location, and runs.

## Run now and inspect results

Choose **Run now** from the Automation's menu to run its current instructions. Open an entry in **Runs** to inspect the conversation and result.

Runs belong to the Automation's owner. Other people may see artifacts on a shared Canvas without seeing the private run conversation.

## Pause or resume

Click the **Active** status to pause an Automation, or use **Pause** from its menu. Pausing retains the schedule and instructions.

Resume a paused Automation with **Resume** or its status control. An Automation without a schedule needs a cadence before it can recur.

Pausing prevents future scheduled starts. It doesn't stop a run already in progress; open that run's conversation if you need to stop it.

## Edit or duplicate

Edit the name, instructions, schedule, time zone, or **Runs on** selection, then save your changes. They affect subsequent runs.

An Automation's location is fixed. **Duplicate** creates another configuration in the same location. To use a different Workspace or Canvas, create a new Automation and select that location. Review a copy's schedule and instructions before relying on it.

Only the owner can change, run, or inspect the private run history of an Automation.

## A run didn't happen

Check:

* **Status and schedule.** Confirm that it is active and has a future run time in the intended time zone.
* **Access.** The owner needs edit access to the target Workspace or Canvas, and the location must still be available.
* **Connections.** Reconnect any app or model provider whose authorization has failed.
* **Usage.** Cohesive usage checks still apply, including when a connected subscription pays for model tokens.
* **Run history.** Open the latest entry for the recorded outcome.

Loss of access to the target can pause scheduling. A billing denial can skip a run while keeping its cadence.

## A run is waiting for input

Open the run and review its question or command confirmation. Clarify the instructions for future runs if they leave an important decision unresolved.

## Remove an Automation

Use **Delete** only when you no longer need its saved configuration. Use **Pause** when you want to keep it for later; Automations aren't restored through the Archive.