> For the complete documentation index, see [llms.txt](https://documentation.taskmaverick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.taskmaverick.com/analytics-and-monitoring/overview/schedules-and-timeline.md).

# Schedules and Timeline

Three Overview views help you plan and manage future work: **Scheduled** shows what's planned, **Timeline** visualizes when it happens, and **Deployed** shows what's currently published for Processes.

***

## Scheduled

Go to **Overview → Team or Personal Board → Scheduled**.

Shows all Missions with active schedules — and optionally idle (unscheduled) Missions too.

### What you see

<table><thead><tr><th width="208">Column</th><th>What it shows</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Mission name</td></tr><tr><td><strong>Start / End</strong></td><td>Schedule start and end dates</td></tr><tr><td><strong>Repeat</strong></td><td>Recurrence pattern</td></tr><tr><td><strong>Time</strong></td><td>When the Mission posts each day</td></tr><tr><td><strong>Folder</strong></td><td>Which Library folder it belongs to</td></tr></tbody></table>

### What you can do

* **Edit Schedule** — modify timing or destination
* **Clear Schedule** — stop all future instances
* **Post to Team / Assign to Personal Board** — bulk-schedule selected Missions
* Check **Idle** checkbox to include unscheduled Missions in the view
* Group by Mission, Unit, Team, or Person

{% hint style="warning" %}
Not available for Ticket Boards — Tickets are triggered, not scheduled.
{% endhint %}

***

## Timeline

Go to **Overview → Team or Personal Board → Timeline**.

A visual, chronological view showing **when Missions post** and **how often they repeat** — displayed as colored blocks across a time grid.

### Three views

<table><thead><tr><th width="130.3333740234375">View</th><th>Shows</th><th>Best for</th></tr></thead><tbody><tr><td><strong>1D</strong></td><td>Hour-by-hour within a single day</td><td>Checking daily workload density</td></tr><tr><td><strong>7D</strong></td><td>Day-by-day across one week</td><td>Validating weekly routines</td></tr><tr><td><strong>31D</strong></td><td>Day-by-day across one month</td><td>Long-term planning</td></tr></tbody></table>

### What you can do

* **Copy Schedule** — copy a Mission's schedule to another team or location (single or bulk)
* **Clear Schedule** — stop all future instances
* **Edit Schedule** — modify timing
* Filter by specific hours to zoom into busy periods

**Example:** A new restaurant opens. The manager opens Timeline for the existing location, bulk-copies all 30 Mission schedules, and pastes them to the new location — done in 2 minutes.

***

## Deployed

Go to **Overview → Process Board → Deployed**.

Shows all **Published** Processes with their Triggers — Active, Paused, or Broken. From here you can:

* Create new schedules for a Process
* Edit existing schedule destinations
* Clear schedules
* Pause or resume individual Triggers

The Timeline section (1D, 7D, 31D) is available for Schedule Triggers, showing when Process instances will fire.

***

## Good to know

* Scheduled and Timeline views are **not available** for Ticket Boards
* Exports support up to **300,000 records** — filter if your table exceeds this
* All three views are **web only**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.taskmaverick.com/analytics-and-monitoring/overview/schedules-and-timeline.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.