kylebennison
New Contributor II

@AxelM I see this was a while ago, what was your solution? In my experience, either the `source` field under notebook task is incorrectly set to "WORKSPACE" instead of "GIT", or there's a legitimate issue, such as:

  • a typo/mismatch between the specified path and the actual path
  • a tag, branch, etc. which the job was originally deployed to target has been changed or deleted

@ROTT 

The Jobs API does not accept Git refs/tags—only absolute workspace paths allowed

This is not accurate.

From the docs, we see the jobs create API takes a git source option: https://docs.databricks.com/api/workspace/jobs/create#git_source

When that is specified, then other tasks, such as notebook task, require a relative reference, as OP correctly pointed out.

The notebook task parameter specifies that you must use relative paths if using git-source: https://docs.databricks.com/api/workspace/jobs/create#tasks-notebook_task-notebook_path