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

# Sequences

> Create, schedule, pause, run, and review recurring Sofie workflow automation with Sequences.

Sequences run an Orchestration once or on a recurring schedule. Use them when the same Sofie workflow should happen later, repeat on a cadence, or notify you when a scheduled process needs attention.

<Note>
  Sequence appears only when your organization enables it. If you do not see **Sequence** in **Create**, the feature may not be available for your account.
</Note>

## When to use a Sequence

Use a Sequence when the trigger is time-based.

Good uses:

* Weekly Workspace summary.
* Daily open issue triage.
* Recurring meeting follow-up digest.
* Scheduled review of new Workspace content.
* Periodic status report generation.
* Routine evidence collection before a review meeting.

Use an Orchestration without a Sequence when the workflow should run only when a user starts it.

## How a Sequence works

A Sequence includes:

| Part          | What it does                                                                      |
| ------------- | --------------------------------------------------------------------------------- |
| Name          | Identifies the scheduled workflow.                                                |
| Description   | Explains what the Sequence does and when it should run.                           |
| Orchestration | The workflow the Sequence runs.                                                   |
| Inputs        | Values, files, Workspaces, or other inputs passed into the Orchestration.         |
| Schedule      | A one-time or recurring run time.                                                 |
| Status        | **Active** runs on schedule. **Paused** does not.                                 |
| Test Run      | Starts a run so you can verify inputs and outputs before relying on the schedule. |

## Create a Sequence

<Steps>
  <Step title="Open Sequence">
    Go to **Create** and choose **Sequence**.
  </Step>

  <Step title="Create or open a Sequence">
    Click **Create** or open an existing Sequence from the list.
  </Step>

  <Step title="Name it clearly">
    Use a title that explains cadence and purpose, such as `Weekly PPQ Workspace summary`.
  </Step>

  <Step title="Add a description">
    State what the Sequence does, which Workspace or process it covers, and who reviews the result.
  </Step>

  <Step title="Select an Orchestration">
    Choose the Orchestration that should run.
  </Step>

  <Step title="Fill inputs">
    Provide required inputs such as Workspace, files, product, process, date range, or output destination.
  </Step>

  <Step title="Add a schedule">
    Choose a one-time or recurring schedule and confirm the timezone.
  </Step>

  <Step title="Test before activating">
    Run a test and review the output before switching the Sequence to **Active**.
  </Step>
</Steps>

## Choose the right Orchestration

The Orchestration should already work well before you schedule it.

Before using an Orchestration in a Sequence, confirm:

* Required inputs are clear.
* Source rules are specific.
* Human review points are defined.
* Outputs are structured enough for repeat use.
* Test runs pass with realistic inputs.
* Failure modes are understood.

Use [Test Orchestrations](/orchestrate/test-orchestrations) before scheduling important workflows.

## Configure inputs

Sequence inputs should be stable enough to reuse.

Good inputs:

* A Workspace that always contains the relevant project files.
* A recurring date range such as the previous week.
* A report title pattern.
* A defined output destination.
* A review owner or team.

Risky inputs:

* A one-off file that may be deleted.
* A broad Workspace with unrelated content.
* A vague source rule such as `use all documents`.
* A destination that many users can edit unexpectedly.

<Tip>
  If the Sequence should review changing Workspace content, keep Workspace folders clean and use clear source rules in the Orchestration.
</Tip>

## Schedule a Sequence

You can schedule a Sequence:

| Schedule type | Use it when                                                 |
| ------------- | ----------------------------------------------------------- |
| Once          | The workflow should run at a specific future date and time. |
| Recurring     | The workflow should repeat automatically.                   |

Recurring schedules can use common day choices such as weekdays, weekends, or a specific day. Advanced users may see custom schedule expressions.

Always confirm:

* Timezone.
* Next run preview.
* Whether the Sequence should stop after a maximum number of runs.
* Whether the Sequence should be active immediately or paused for review.

## Use Test Run

Use **Test Run** before relying on a Sequence.

Test Run helps you verify:

* The selected Orchestration is correct.
* Inputs resolve as expected.
* The Workspace or files are accessible.
* Output format is usable.
* Review points appear in the right place.
* Notifications arrive as expected.
* The run does not create or save unintended content.

<Warning>
  Test Run may still execute the configured workflow. Review the Orchestration and inputs before testing a Sequence that creates, saves, sends, or updates content.
</Warning>

## Active and paused states

Use **Paused** while you are designing, testing, or fixing a Sequence.

Use **Active** only when:

* The Orchestration has been tested.
* Inputs are correct.
* The schedule is correct.
* The output destination is correct.
* Review and notification behavior is acceptable.
* The owner knows how to respond to failures.

Pause a Sequence when:

* Source folders are being reorganized.
* The Orchestration changed.
* The schedule is no longer needed.
* The output destination changed.
* A recent run produced unexpected output.

## Review Sequence notifications

Sequence notifications can alert you when:

* A Sequence starts.
* A Sequence completes.
* A Sequence fails.
* A Sequence needs human review.
* A Sequence step fails.
* A schedule is disabled.

Use [Notifications](/notifications/notifications) to manage these alerts.

## Sequence examples

### Weekly Workspace summary

```text theme={null}
Create a Sequence that runs the Workspace summary Orchestration every Friday at 9:00 AM Pacific. Use the PPQ Workspace. Output a CoDraft with new files, open questions, completed work, and next actions. Keep it paused until I review a test run.
```

### Daily open issue triage

```text theme={null}
Create a weekday Sequence for open deviation follow-up. Use the quality triage Workspace. Summarize new items, owner blockers, source gaps, and items that need SME review.
```

### Recurring meeting follow-up

```text theme={null}
Create a Sequence that runs every Monday morning to summarize CoMeetings from the prior week and prepare action items for the project Workspace.
```

## Troubleshooting

<Accordion title="The Sequence did not run">
  Check whether it is **Active**, whether the schedule time has passed, whether the timezone is correct, and whether the selected Orchestration is still available.
</Accordion>

<Accordion title="The Sequence used the wrong files">
  Review the Orchestration source rules and the selected Workspace. Narrow the folder, file type, date range, or source criteria.
</Accordion>

<Accordion title="The Sequence failed">
  Open the failed run, check missing inputs or access issues, then run a test before activating the schedule again.
</Accordion>

<Accordion title="The output is too noisy">
  Narrow the Orchestration, split the workflow, or use Structured Outputs so each run produces predictable fields.
</Accordion>

<Warning>
  Scheduled work can repeat mistakes. Keep important Sequences paused until test runs show the right sources, outputs, review points, and destinations.
</Warning>