Schedule conflicts between project tasks

Release version: Australia

Updated March 12, 2026

2 minutes to read

Summarize

Summarized using AI

Summary of Schedule Conflicts Between Project Tasks

Scheduling conflicts help identify project tasks that do not honor dependencies. A conflict arises when one task's scheduling prevents another from starting on the specified date due to dependencies or constraint types. The system provides a warning when this occurs, allowing you to either cancel the conflicting action or proceed, knowing that the constraint date will take precedence.

Show full answer Show less

Key Features

Conflict detection: The system alerts you to scheduling conflicts when dependencies or constraints are not met.
Decision-making options: You can cancel the action causing the conflict or proceed, resulting in recalculated dates.
Visual indicators: Conflicts are marked with a red calendar icon in both client-side and server-side planning consoles.
Task management: Adjusting constraint types (e.g., to Start ASAP) allows tasks to honor dependencies and adjust their start dates accordingly.

Key Outcomes

By understanding and managing scheduling conflicts, you can ensure that project tasks are aligned with their dependencies and constraints, leading to more efficient project scheduling. Identifying conflicts in the planning console allows for timely adjustments, minimizing disruptions in project timelines.

Scheduling conflict helps you to identify project tasks that are not honoring dependencies. A scheduling conflict occurs when one project task prevents other task from starting on the specified date because of dependencies or constraint types.

A scheduling conflict occurs when any action such as applying a dependency, changing constraint type, or constraint date causes the task start date to violate the project's constraint date.

When a scheduling conflict occurs, the system warns you about the conflict. You can choose to cancel the action that is causing the conflict or continue with the conflict. If you choose to continue with the conflict, the constraint date is given highest precedence and dates are recalculated. The start date is moved till allowed by the task constraint date, but dependency is not honored.

For example, consider the following scenario:

For a project with project task's Constraint date set as 20 January, there are two tasks:

T1 with constraint type set to As soon as possible and start date of 20 January.
T2 with constraint type set to Start no later than and start date of 20 January.

If you add an FS dependency between tasks T1 and T2, the task T2 should start on 21 January, but due to Start no later than constraint, task T2 cannot start on 21 January. This inability of starting task T2 on the specified date is an example of conflict.

In this example, if you choose to proceed with the conflict, the start date of task T2 is moved to 20 January which is the constraint date.

Scheduling conflict between tasks is shown for tasks with Start no later than and Start on specific date time constraints.

If you want the task to honor the dependency and adjust the start accordingly, change the constraint type of the task to Start ASAP.

When a scheduling conflict is identified, you can identify such tasks in the planning console.

The client-side planning console displays a pop-up message with an option to proceed with the conflict or cancel the action. If you proceed with the conflict, the constraint type is applied or date is changed appropriately to the next feasible date.
The calendar icon () on the client side planning console changes to red () to indicate the conflict.
The calendar icon on the server side planning console changes to red () to indicate the conflict.