- Asana task dependencies break in predictable ways — plan-tier gating, template inheritance failures, recurring task resets, cross-project date cascade limitations, and the approval task enforcement gap.
- Most failures have documented causes that Asana’s help docs underplay.
- This guide covers all 8 failure modes with the fixes that actually work in 2026.
- The Architecture Behind Asana Dependencies
- Issue 1: Dependencies Greyed Out or Missing
- Issue 2: Dates Don’t Shift When a Dependency Completes
- Issue 3: Template Tasks Lose Dependencies
- Issue 4: Recurring Task Dependencies Reset on Each Recurrence
- Issue 5: Cross-Project Dependencies Don’t Update Dates
- Issue 6: Approval Task Dependencies Not Enforced
- Issue 7: Can’t Find Tasks to Add as Dependencies
- Issue 8: Dependency Arrows Missing in Timeline View
- Frequently Asked Questions
The Architecture Behind Asana Dependencies
Asana dependencies are relational markers, not enforcement gates. Marking Task B as dependent on Task A adds a visual arrow in Timeline, marks Task B as “waiting on” Task A, and — on the right plan — optionally shifts Task B’s due date when Task A’s date changes. What Asana does not do is prevent someone from completing Task B before Task A. This is a deliberate product decision. If you need hard enforcement, you need a Rules automation — typically one that reassigns or blocks tasks whose dependencies are unresolved.
Issue 1: Dependencies Greyed Out or Missing
Task dependencies are gated behind the Advanced plan. On Free or Starter, the dependency UI elements don’t appear. Before assuming a plan issue, verify: the “Dependencies” section appears in the task detail panel when you scroll down in the side panel. If the section doesn’t exist, you’re on a plan that doesn’t support them. If the section exists but the button is greyed out, check Project Settings → Features → Dependencies to ensure the feature is enabled for that specific project.
Issue 2: Dates Don’t Shift When a Dependency Completes
Date shifting is not automatic — it requires a manual confirmation. When a task with dependents is completed and its due date was overdue, Asana surfaces a dialog asking whether to shift dependent task dates. If that dialog is dismissed, no shifting occurs and there’s no way to retroactively trigger it. You must manually update the dependent task’s due date.
The Date Shift Workflow That Actually Works
- Use Timeline view when completing tasks with dependencies — the shift dialog only reliably appears in Timeline, not in Board or List view
- When the shift dialog appears, review proposed new dates before confirming — Asana calculates based on original task duration, which may not match your intent
- For automatic date shifting without manual prompts, pair Asana with Zapier to trigger date updates programmatically when task status changes
Issue 3: Template Tasks Lose Dependencies
This is a documented platform bug. When tasks are created from a task template that has dependencies defined, the dependencies frequently don’t copy to the new tasks. The template shows them correctly; the instantiated tasks don’t have them. The workaround: build dependencies in a project template (not a task template). Project templates copy dependencies reliably. Task templates do not. Convert your task templates to project templates if you need recurring workflows with dependencies.
Issue 4: Recurring Task Dependencies Reset on Each Recurrence
This is by design. When a recurring task is marked complete, Asana creates a fresh task instance for the next recurrence. Dependencies from the completed instance don’t carry over — Asana treats each recurrence as a new task. The fix: don’t use Asana recurring tasks for dependency-driven workflows. Instead, use project templates that you manually instantiate for each cycle, or use Rules to automatically create and link dependent tasks on a schedule.
Issue 5: Cross-Project Dependencies Don’t Update Dates
Asana supports cross-project dependencies but with a significant limitation: date cascade shifts don’t propagate across project boundaries. A delay in Project Y won’t auto-shift dates in Project X — you’ll get the visual dependency warning but not automatic date adjustment. For programs where cross-project scheduling is critical, this is a genuine product gap. Teams managing complex multi-project timelines often supplement Asana with a dedicated scheduling tool or use Smartsheet for the scheduling layer.
Issue 6: Approval Task Dependencies Not Enforced
Dependencies on approval subtasks work inconsistently based on how the approver completes the action. Opening the subtask directly and approving respects the dependency. Approving from the parent task’s subtask list bypasses dependency logic. This was reported by multiple users in late 2024 and persists in 2026. Workaround: instruct approvers in your SOPs to always open each approval task directly before acting — it’s a process guardrail while Asana addresses the underlying behavior.
Issue 7: Can’t Find Tasks to Add as Dependencies
The dependency picker’s search scope is limited to the current project and recently viewed tasks. Tasks from other projects you haven’t recently interacted with won’t appear in suggestions unless you type the exact task name. For cross-project dependency assignment with limited search results, navigate to the other project directly, open the task there, and add the dependency using “This task is blocking” from that task’s detail panel instead.
Issue 8: Dependency Arrows Missing in Timeline View
Dependencies exist but Timeline doesn’t show the connecting arrows. Check two things: (1) the Dependencies toggle in Timeline view options (top-right gear icon) — it must be enabled to show arrows, and (2) tasks without both a start date AND due date assigned won’t display arrows even if the dependency relationship exists. Timeline requires date spans to draw the connecting line. Assign both start and due dates to all tasks in your dependency chain to make the arrows appear.
📚 Related Reading on WorkManagement Hub
🔗 Official Resources
Frequently Asked Questions
No. Asana dependencies are informational, not enforcement gates. A user can complete Task B even if Task A is incomplete — Asana shows a warning but won’t block the action. For hard enforcement, use a Rule to automatically reassign or add a “Blocked” custom field to tasks with unresolved dependencies.
Known bug with task templates — dependencies in task templates frequently don’t transfer to instantiated tasks. Use project templates instead, which copy dependencies reliably. Manually re-add dependencies after task template instantiation until Asana resolves this at the platform level.
Yes, cross-project dependencies are supported on the Advanced plan. However, date cascade shifts don’t propagate cross-project. You’ll get the visual dependency indicator but not automatic date adjustment when predecessor dates change.
By design. Each recurrence is a fresh task instance — Asana doesn’t copy dependency relationships to new occurrences. Use manually instantiated project templates for recurring workflows that require dependencies.
🎯 Expert Bottom Line
Asana’s dependency system is visibility-first, not enforcement-first — understanding that distinction resolves most confusion. The two issues causing the most pain are the task template inheritance bug (use project templates) and the recurring task dependency reset (don’t use recurring tasks for dependency-driven workflows). If you need hard blocking enforcement or reliable cross-project date cascades, Asana’s current implementation requires workarounds. Smartsheet or Microsoft Project handle complex dependency graphs more robustly when that’s central to your workflow.
