Workflow Errors

Also, It would be very helpful to have a way to handle exceptions within the workflow. Such as if a Send Email action errors with RequestorId:
db1a50a9-b795-8b5e-0000-000000000000. Details:
System.Activities.Statements.WorkflowTerminatedException: The message could not be delivered to one or more recipients.

Because the user didn't have an email box. This errors the workflow and must be restarted. Could we capture exceptions by the workflow and use the "If Error" technique used on prem?

It would be very good to have this same ability added to SharePoint on-prem.

That would be a great feature! Including the Workflow Error in the body of the e-mail would make it even better!

I am surprised how Nintex missed this on SharePoint online.

We're migrating to SharePoint Online from SharePoint 2010 and I have been extremely disappointed with the things that are missing and how much more difficult it is to build a workflow. We have so many users starting workflows, we really need an error notification to go to someone so we can fix issues.

This is degraded function in Office 365 vs On-Prem. We need it back.

I have a similar error when the send email activity causes the whole workflow to finish.
Not having the possibility to try/catch such errors is a big problem.
//Oliver Lopez

We need this back. By not having it, it makes this not enterprise ready. Having to manually check the workflow health (which you need to be an owner of the site to do) is just crazy.

Agree, we need this ASAP.

Yes, especially as the workflow health option page that seems to help with this often provides wrong information so just provides more confusion

yes. Its a must feature. Please add in your feature release.

If a workflow gets suspended or errors for any reason, it should be possible to get a notification so that I can go back and check what caused the error or so that I can restart the workflow.

Something like what is described here (http://sharepoint.stackexchange.com/questions/85037/handling-workflow-errors) where you take advantage of the workflow history list to catch errors and send alerts would be nice, or something more built in to nintex could be good as well.

Similar to this idea - https://nintex.uservoice.com/forums/218291-3-nintex-workflow-for-office-365/suggestions/13542516-error-if-sending-to-invalid-external-email - but if a response was captured in a variable that would be better than the workflow terminating with no details.

I want to make sure that their is a valid/active User Profile. If there's not, I want to do something different; I don't want the workflow to error and end.

I have a workflow that sends emails to multiple users. I found out the hard way that if a users account is removed, any time a workflow action attempts to send an email to this user account the entire workflow instance will be terminated. This is challenging considering the large number of deployed workflows that send emails.

Is it possible to include in future releases the ability to handle this type of exception so that the workflow can continue with sending the email to the other recipients and move on to later actions in the workflow instead of terminating with an error?

Failing Actions should not stop the workflow.

In the following error message, there is an issue in a specific activity. The error handler knows what activity caused the issue by providing the GUID. The designer is unable to determine which activity/action caused the issue as the designer does not display the matching GUID. Instead, can the Title of the action or some other information of the action be displayed in the error message?

Error publishing workflow. Workflow XAML failed validation due to the following errors: Object reference not set to an instance of an object. HTTP headers received from the server - ActivityId: a41a30d5-c786-4546-bdde-e03903af1796. NodeId: . Scope: . Client ActivityId : ede2f19c-7043-1000-b4b2-37a9eab76b50. The remote server returned an error: (400) Bad Request.

At one of out customers 1% of all workflow get stuck while setting (group) permissions to the current list item. After the 5 retries the workflow stops. It shou retry again after a certain period and allow and admin to retrigger a new retry from the Workflow Status screen.

We have some workflows which some times get terminated or suspended ...It would be great if we can be notified for such failures via email

This is GREATLY need in SharePoint on-prem as well.....