metricsign
Start free
Medium severityconfigurationMicrosoft Fabric

Power BI Refresh Error:
Fabric Pipeline Error 3201

What does this error mean?

The Fabric Data Pipeline Databricks activity failed because a required field — typically the notebook path or task settings — is missing or incorrectly authored in the pipeline configuration. The job cannot be submitted to Databricks without this field.

Common causes

  • 1The notebook path field in the Databricks Notebook activity was left blank or contains an invalid path format
  • 2A pipeline was copied or imported and the Databricks task settings were not updated to point to a valid notebook in the target workspace
  • 3Dynamic expressions used for the notebook path resolved to null or empty string at runtime due to a missing pipeline parameter
  • 4The activity JSON was hand-edited and a required settings property was accidentally removed

How to fix it

  1. 1Step 1: Open the failing pipeline in the Fabric Data Factory editor and navigate to the Databricks Notebook activity settings.
  2. 2Step 2: Verify the 'Notebook path' field is populated with a valid absolute path (e.g., /Users/user@domain.com/MyNotebook) that exists in the connected Databricks workspace.
  3. 3Step 3: If the path is set dynamically via a parameter or variable, add a debug run with sample values to confirm the expression resolves to a non-empty valid path.
  4. 4Step 4: Browse the Databricks workspace file browser to confirm the notebook exists at the specified path and has not been moved or deleted.
  5. 5Step 5: Save and validate the pipeline, then trigger a manual run to confirm the error is resolved.

Frequently asked questions

Does error 3201 only relate to missing notebook paths?

The error covers any missing required field in the Databricks task settings block, which can include the notebook path, cluster settings, or other mandatory activity properties depending on the activity type configured.

Can this error appear after a Databricks workspace migration?

Yes — if a notebook was migrated to a new workspace with a different path structure and the pipeline was not updated accordingly, the stored path becomes invalid and will trigger this error on the next run.

Other configuration errors