> For the complete documentation index, see [llms.txt](https://www.usemotion.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.usemotion.com/help/project-management/task/reference-tasks.md).

# Reference: Tasks

## Introduction

Tasks in Motion are the core unit of work. Unlike events, which mark fixed time commitments, tasks are flexible blocks that Motion can schedule dynamically based on deadlines, priorities, and your defined schedule. Tasks can recur, adapt, and shift as your calendar changes, ensuring your work aligns with available time.

#### At a Glance

* **Tasks vs Events** → Tasks are flexible work units that Motion can move and reschedule around your availability. Events are fixed commitments tied to a specific time and synced directly with external calendars.
* **Recurring tasks** → Motion supports daily, weekly, monthly, and custom recurrence cadences, ensuring repetitive work is automatically placed without manual re-entry.
* **Benefits of recurring tasks** → Reduces repetitive setup, enforces consistency for routines, and keeps long-term workflows reliable.
* **Free vs Busy** → Tasks are always dynamically scheduled, but marking them as **Free** lets other events overlap the same time, while **Busy** prevents overlaps by holding that slot.
* **Auto-archiving** → Completed tasks are automatically archived after a set period, keeping your task lists clean without manual cleanup.
* **Manual archiving** → Users can manually archive tasks that no longer need visibility but should remain in the workspace history.
* **Troubleshooting scheduling** → If a task doesn’t appear where you expect, Motion provides clear reasons (e.g., missing duration, conflicting deadlines, blocked by calendar events) to help you adjust.


---

# 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://www.usemotion.com/help/project-management/task/reference-tasks.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.