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

# Schedule & history

> Control when each step sends, see what's coming up, and review everything that's already gone out.

Every step in a sequence sends on a schedule. You set the timing in the Editor, and track
what's upcoming and what's already happened from the Schedule and History tabs.

## Timing a step

Each step has its own timing, set relative to the step before it:

<Steps>
  <Step title="Delay">
    Choose how long to wait after the previous step, counted in **business days** (skipping
    weekends) or **any days**.
  </Step>

  <Step title="Send time">
    Pick the time of day the step should go out.
  </Step>

  <Step title="Time zone">
    Set the time zone the send time is based on, so messages land at a sensible local hour.
  </Step>
</Steps>

<Note>
  The "message after connection accepted" step is the exception. It sends when the candidate
  accepts your request rather than after a fixed delay. See [Sequence steps](/sequences/steps).
</Note>

Clarvo also paces sending so a batch of messages goes out gradually rather than all at once,
which keeps your outreach looking natural.

## Schedule tab: what's coming up

The **Schedule** tab shows the **upcoming steps** queued to send, and when. It's the easy way
to see what each contact will receive next. A project-wide schedule view also rolls up the
upcoming steps across all of your sequences.

## History tab: what's already gone out

The **History** tab is the record of every step that's been processed, each with a status:

| Status        | Meaning                                                                                    |
| ------------- | ------------------------------------------------------------------------------------------ |
| **Scheduled** | Queued to send.                                                                            |
| **Sent**      | Delivered to the candidate.                                                                |
| **Failed**    | Couldn't be sent.                                                                          |
| **Bounced**   | An email bounced back (invalid or rejected address).                                       |
| **Cancelled** | Won't send: for example, the candidate replied, so the rest of their steps were cancelled. |

A project-wide history view shows activity across all sequences in one feed.

<Tip>
  If a step failed, check that the right account (email or LinkedIn) is still connected,
  then retry it from history.
</Tip>