> 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/meeting-events/reference-meeting-events/conflicts-and-overrides.md).

# Conflicts & Overrides

Events in Motion always take precedence over tasks. Because events represent fixed commitments, Motion resolves overlaps by protecting the event and shifting tasks.

**Behavior**

* **Event vs Task** → If an event and a task overlap, the **event wins**. Motion reschedules or flags the task. Two events can overlap one another, Motion will not reschedule if an existing event is already scheduled.
* **Multiple events** → When two events overlap, Motion mirrors whatever is set in the external calendar (e.g., double-booked meetings remain double-booked in Motion).
* **Free events** → Tasks can be scheduled on top of events marked *Free*, since they don’t block time.
* **All-day events** → Block the full day if marked *Busy*; no tasks are scheduled. If marked *Free*, Motion can still schedule tasks during that day.
* **Tentative events** → Treated as *Busy* unless declined or removed externally.
* **Declined events** → Do not block tasks and disappear from your active calendar view in Motion.

**Why it matters**\
Conflicts are resolved consistently to protect your calendar integrity: **events anchor your schedule, tasks flex around them.**


---

# 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/meeting-events/reference-meeting-events/conflicts-and-overrides.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.
