👋 Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you are looking for the Nintex roadmap, you can find that on Nintex Community
If you have questions about Nintex Ideas, please contact firstname.lastname@example.org
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact email@example.com
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?
Not having the possibility to try/catch such errors is a big problem.
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.
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?
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.