- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2022 09:38 AM
This morning I encountered an issue when trying to create a new job using the Workflows UI (in browser). Never had this issue before.
The error message that appears is:
"You are not entitled to run this type of task, please contact your Databricks administrator to learn more."
The admin at our company claims they changed nothing, so it's likely caused by a failed upgrade.
Screenshot of the problem:
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-10-2022 02:38 AM
Hi @Robbie Capps, thanks for reaching out.
We are aware of this situation, and the engineering team is working on a fix. The fix will come out in the next scheduled upgrade on your shard.
Impact: Non-admin UI users in the single-tenant shards will not be able to create a new job, add a task to an existing job or change the type of an existing task. This issue only affects the UI. API users are not affected and can continue to perform the aforementioned Job actions.
Workaround: Our engineering team proposes three workarounds:
- Any non-admin user can ask an admin user to perform the tasks on their behalf.
- Any non-admin users can be upgraded to an admin user until the issue is fixed.
- The issue is happening only in UI. Hence you can use APIs to perform the mentioned tasks till the time issue is fixed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-10-2022 02:38 AM
Hi @Robbie Capps, thanks for reaching out.
We are aware of this situation, and the engineering team is working on a fix. The fix will come out in the next scheduled upgrade on your shard.
Impact: Non-admin UI users in the single-tenant shards will not be able to create a new job, add a task to an existing job or change the type of an existing task. This issue only affects the UI. API users are not affected and can continue to perform the aforementioned Job actions.
Workaround: Our engineering team proposes three workarounds:
- Any non-admin user can ask an admin user to perform the tasks on their behalf.
- Any non-admin users can be upgraded to an admin user until the issue is fixed.
- The issue is happening only in UI. Hence you can use APIs to perform the mentioned tasks till the time issue is fixed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2022 12:17 PM
@Kaniz Fatma @Philip Nord, thanks!
I was able to do what I needed by cloning an existing job & modifying. It's fine as a temporary fix for now.
Thanks again for the response-- good to know you're aware of it & this isn't anything on my end.

