How to exit the entire job in the orchestration scenario?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ08-10-2022 06:01 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ08-11-2022 07:43 AM
As of now there is no way to stop the present cell after a successful run in "run all" scenario.
Additionally, you can always put an error in the cell where you want run all to stop since errors stop "run all".
Also, you can run all cells above and run all cells below. For example: If you want to run all cells up to cell X, go to cell X+1 and โrun all cells aboveโ.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ09-08-2022 04:36 AM
Hi there @Peiran Quanโ
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
โ04-10-2023 04:12 PM
@Vidula Khannaโ @Vidula Khannaโ
We are experiencing the same issue in our Workflows and I was wondering if there has been any update.
We need the functionality to call a method similar to `dbutils.notebook.exit` in a notebook that will cancel the execution of all the following dependent Tasks or the Job as a whole, but this does not seem to exist in Databricks.
For example,
In the following Example Job, if a certain criteria is met in the Task_1 notebook then I want the Example Job to Stop without firing an error. The idea is that we wouldn't have to waste any unnecessary execution in Task_2 and Task_3.
Is there a way to make a feature request or are there plans to implement this functionality already?

