Action may cause a scheduling conflict because a task is linked but cannot move
The task that you're changing is linked to another task. At some earlier time, this task was linked to another task so that this task could not start or finish until the linked task had started or finished. However, the change that you're making now will constrain the indicated task to a specific start or finish date. This may create a scheduling conflict, either now or later, because the linked task will no longer be able to drive this task's start or finish.
You can avoid this potential scheduling conflict by canceling this action with the Planning Wizard. Alternatively, you can avoid the conflict by setting a flexible constraint, which will still allow the task's dates to be driven by the task to which it is linked.
Note: Go to Link tasks in a project for additional information.
Using the Planning Wizard, you can:
Cancel the action and avoid the scheduling conflict.
Microsoft Project will not change the task, and there will be no potential scheduling conflict.
Continue the action, setting a flexible constraint.
Project constrains this task with a flexible constraint. The task is constrained to the specified date, unless the linked task forces this task's dates to change. The linked task still drives this task's dates.
Continue the action, setting an inflexible constraint, and allow the scheduling conflict.
Project will change the task and a scheduling conflict may occur. Project will not be able to adjust the task's dates to reflect changes in the linked task's dates.
If you don't want the Planning Wizard to display this information again, select the Don't tell me about this again check box.