It was already completed, deferred or canceled
How you'll know: The predecessor slipped and one task further down the chain kept its old date.
Fix: Wrike only reschedules active tasks. Anything completed, canceled, deferred or deleted is skipped, and the chain beyond it can look broken. Reopen it, or relink around it.
A date constraint is holding it
How you'll know: The task won't come earlier when its predecessor finishes early.
Fix: A date constraint sets the earliest a task can start, and Wrike won't pull it before that. Clear the constraint if the date isn't truly fixed.
The link points the wrong way
How you'll know: Moving the task you expected to drive the schedule pushes nothing, and moving its successor pushes it instead.
Fix: Open the dependency and check which task is the predecessor. Start to finish is the easy one to set by mistake.
The real deadline lives elsewhere
How you'll know: A delivery or permit date changed in another system, and the Gantt chart still shows the old plan.
Fix: Make that date its own milestone, link the dependent tasks to it, and have the system that owns it update it. The Wrike API can write task dates, so a sync can do that.