Throw Error Activity
If my pipeline orchestrates an asynchronous operation like processing an Azure Analysis Services model that the pattern is to start the operation asynchronously then loop and check the status. If the status is failed the REST API just says status=Failed but the REST API does not return an HTTP 500 status code so ADF does not fail. So I need a new Throw Error Activity component that will let me build an expression for the ErrorMessage property and throw an error message. Better yet there would be a property which does not throw an error if the property is set to false but does throw an error if the property is set to true.
Greg Galloway
shared this idea
8 comments
-
Nick McDermaid
commented
Great minds think alike - I am doing exactly the same thing. I think I'll do a database call with RAISERROR. Nasty but I'm already working around the fact that you can't capture refreshId directly from the initial REST call. If we got raiserror capability in ADF and conditional workflow it would make all of my pipelines waaaay simpler.
-
Gaurav Gangwar
commented
Please add some error handling feature in DF only.
Because most of the time it's not allowed to use Logic App.
-
pavaniroy
commented
how to do the error handling of the pipelines in azure datafactory
-
kbaig109
commented
Definitely need the error component to show the red pill ... my if condition fails but the activity success connector turns true and the next dependent activity gets executed .. completely agree with Mark said about how that activity should work .. just raise an error and show a red pill to notify .. Thanks
-
Vinayak
commented
These are basic features that is required when performing ELT operations. You need to add this feature on priority.
-
Mark
commented
I need this too for an IF activity. I get how a specific activity could do this but your "better still" comment, not sure how this would be implemented because there are 4 possible scenarios.
The activity generated and error and do we throw or not throw.
The activity generated no error and do we throw or not throw..My 2c would say have an activity whose only job is to create an error output (the red pill :-) ). This can be placed anywhere but especially useful in an IF activity on either the true or false branch.
-
Francisco
commented
It would be good to have an activity that forces the pipeline to fail with a customized error message that could be used, for example, within an If Condition activity and thus would trigger an alert that we have configured for when the pipeline fails. This way we can receive a notification email with the message cause pipeline fails.
-
Lalit Rana
commented
There are situations while orchestrating control flow to fail the parent or entire pipeline based on certain error. Either ADF should add this behavior to each activity like SSIS or add another ErrorHandling activity which can fail the parent or pipeline itself.
e.g In ForEach activity there is no way to terminate loop on failure of one iteration.