Is there any way to disable terminating a workflow on error, like an on error resume next? Try catch still cancels the workflow in the try branch.
Question
Question
Answer
Perhaps you can try Adding the error that happens to the Task Error Handler, it'd record a warning. It would also actually wait around and trying to resend the e-mail every five minutes.
By default, it would wait for slightly over 4 hours before giving up and terminating the workflow.
https://answers.laserfiche.com/questions/46919/Workflow-Email-Errors#47627
Or perhaps you can redesign the workflow so it use child workflow to send emails, personally I think having large workflow is not a good idea, better to break them down and let them invoke each other.
Replies
Can you describe your use case more? It sounds like your try-catch needs to be more granular.
A customer has a large workflow with a huge amount of routing activities. Each routing activity sends an email notification. Their email server has been overloaded on some days and the normal solution is to put all email activities (when they exist on their own) in a try catch. In this case, we don't want to cancel the other tasks existing in the routing activity if the email server is not responding. We also don't want to terminate the workflow just because an email server was unavailable. Ideally we would just like email notifications to sit in a queue until the email server is available and process workflow activities in a separate thread.