What causes WORKFLOW_TASK_NOT_FOUND?

A depends_on reference in another task points to a task key that was renamed or removed. A job repair or retry specified a non-existent task key. The job JSON definition was edited manually and a task key was misspelled

How do I fix WORKFLOW_TASK_NOT_FOUND?

Step 1: Open the job definition and review the task DAG for any broken dependency arrows.. Step 2: Check all depends_on fields across tasks to ensure every referenced key exists.. Step 3: If the task was renamed, update all downstream depends_on references to use the new key.. Step 4: Re-save and trigger a manual run to confirm the dependency graph resolves correctly.

High severityconfiguration

Power BI Refresh Error:
WORKFLOW_TASK_NOT_FOUND

What does this error mean?

A Databricks Workflows run failed because a referenced task key does not exist in the job definition, often caused by a misconfigured dependency or a task that was renamed or deleted.

Common causes

1A depends_on reference in another task points to a task key that was renamed or removed
2A job repair or retry specified a non-existent task key
3The job JSON definition was edited manually and a task key was misspelled

How to fix it

1Step 1: Open the job definition and review the task DAG for any broken dependency arrows.
2Step 2: Check all depends_on fields across tasks to ensure every referenced key exists.
3Step 3: If the task was renamed, update all downstream depends_on references to use the new key.
4Step 4: Re-save and trigger a manual run to confirm the dependency graph resolves correctly.

Frequently asked questions

Can I catch this error before a production run?

Yes — use the Databricks Jobs API validate endpoint or run the job once manually in development before promoting the definition to production.

Does this affect jobs created through Terraform or CI/CD?

Yes. If your IaC template references a task key that was removed in an update, the job will fail on the next run. Always lint job definitions in your CI pipeline.