- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2023 09:07 AM
This has been happening for about 2 days now. Any ideas on why this occurs and how it can be resolved. I attached a screenshot.
- Labels:
-
Databricks Workflow
-
JOBS
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2023 06:20 AM
This issue got resolved on it's own, but not sure what the problem was, probably a bug from a software update?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2023 09:15 AM
Hey @Obiamaka Agbaneje] I guess there is some network issue from your side . Can you please create new job and check .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2023 09:31 AM
Hi @Rishabh Pandey thanks for responding. I was able to create a job from a notebook and view it after creation, but not directly from Workflow.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2023 06:37 AM
Can anyone please help with what could possibly be the issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2023 02:50 PM
@Obiamaka Agbaneje Are you able to list the jobs and job runs using rest API?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2023 11:55 PM
Hi @Obiamaka Agbaneje
Hope all is well! Just wanted to check in if you were able to resolve your issue and would you be happy to share the solution or mark an answer as best? Else please let us know if you need more help.
We'd love to hear from you.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2023 06:20 AM
This issue got resolved on it's own, but not sure what the problem was, probably a bug from a software update?