An upstream task in a multi-task job failed, and the dependent task is configured to run only on success. A task dependency condition (e.g., 'run if upstream succeeded') was not satisfied. A conditional task in the job was skipped due to a branch condition not being met. The job run was manually repaired with 'Repair Run' and only failed tasks were re-run — previously successful tasks are skipped

How do I fix SKIPPED?

Identify the upstream task that caused the skip — it is typically the task that failed before the skipped task. Resolve the upstream task failure to allow the full job graph to run. Review the task dependency conditions in the job configuration if the skip was unexpected. If the skip was deliberate (e.g., a Repair Run), verify that the skipped tasks do not need to be re-run

Low severityjob

Power BI Refresh Error:
SKIPPED

What does this error mean?

A Databricks job task was skipped. This is not a failure — the task was intentionally bypassed, either because a preceding task failed and the task dependency condition was not met, or because conditional logic in the job graph excluded it.

Common causes

1An upstream task in a multi-task job failed, and the dependent task is configured to run only on success
2A task dependency condition (e.g., 'run if upstream succeeded') was not satisfied
3A conditional task in the job was skipped due to a branch condition not being met
4The job run was manually repaired with 'Repair Run' and only failed tasks were re-run — previously successful tasks are skipped

How to fix it

1Identify the upstream task that caused the skip — it is typically the task that failed before the skipped task
2Resolve the upstream task failure to allow the full job graph to run
3Review the task dependency conditions in the job configuration if the skip was unexpected
4If the skip was deliberate (e.g., a Repair Run), verify that the skipped tasks do not need to be re-run

Frequently asked questions

Is SKIPPED a failure?

No — SKIPPED is a terminal state that means the task did not run, not that it ran and failed. However, a skipped task may indicate an upstream failure that needs attention.

Can I force a skipped task to run?

Yes — use 'Repair Run' in the Databricks UI and select the skipped task to include it in the repair run. You can also re-trigger the full job.