> For the complete documentation index, see [llms.txt](https://365automate.gitbook.io/365automate-gantt/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://365automate.gitbook.io/365automate-gantt/scheduling.md).
# Scheduling
In this guide, we will cover the core concepts of automated task scheduling. If you are familiar with Microsoft Project, the concepts are very similar.
Auto scheduling can be enabled within Settings > Scheduling:\
Manual scheduling means that when you move a task, that's the date where it stays, and task dependencies are not enforced. Task constraints aren't used at all in manual mode.
#### What is Auto Scheduling?
In a project management environment, auto scheduling describes the capability of the software to **automatically move a task** to accommodate its predecessors and constraints.
For example, if you move a task to a later date, and a successor is configured to start after it finishes, the successor will move to accommodate it.
#### Predecessors/dependencies
A **predecessor** or **dependency** is a task that occurs before the current task. It is linked with a dependency type. Available dependency types are:
* Finish to Start (the task can start when the dependency finishes) - this is the most common type
* Start to Start (the task can start when the dependency starts)
* Start to Finish (the task can finish when the dependency starts)
* Finish to Finish (the task can finish when the dependency finishes)
See the [Dependencies](/365automate-gantt/dependencies.md) guide for more information on creating a dependency.
#### Constraints
A constraint is a boundary on the start or end times of a task. For example:
* **As Soon As Possible** - this is the default.
* **As Late As Possible** - the task will occur immediately before any successors
* **Start No Earlier Than** - start on or after the date
* **Start No Later Than** - start on or before the date
* **Finish No Earlier Than** - must finish on or after this date
* **Finish No Later Than** - must finish on or before this date
* **Must Start On** - a fixed date when the task has to start
* **Must Finish On** - a fixed date when the task has to end.
{% hint style="info" %}
Note than when you manually move a task to a new date, the constraint changes to "As Soon As Possible".
{% endhint %}
To configure a constraint on a task, right-click on it and select Schedule > Constraint type:
A solid black vertical line at the start or end of a task indicates the presence of a "Must Start On/Must Finish On" constraint:
"Must Start On" constraint with a solid line
No visual indicator is shown for "As soon as possible"/"As late as possible".
A dotted line is shown for the remaining constraint types:
A "Start No Earlier Than" constraint
#### Task Manual Scheduling
Changing Task Scheduling to Manual
When Auto Scheduling is enabled, all tasks are re-scheduled as necessary to the relevant dates so as to avoid conflicts.
This icon indicates that the task is taking part in scheduling: 
You can click it to toggle to manual scheduling: 
This indicates that the task will no longer take part in manual scheduling.
If you wish, this column can be removed entirely under **Settings > Data Grid**.
---
# 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://365automate.gitbook.io/365automate-gantt/scheduling.md?ask=&goal=
```
`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.