Yet another question from me. Is there a way to force Workflow into error when it runs out of options during the runtime? Currently when my WFs get into a situation they cant seem to resolve ( Say none of the split conditions apply, or there is no outgoing path) They simply mark themselves as Completed. That seems super wrong. I would like WFs to throw errors instead if they end outside of specified end steps. Is that possible ?
And one more question. Is it possible to somehow configure WF to send an email when it encounters an error ? Currently we have to check for errors manually and that is annoying.
Thank you and have a nice day
Solved! Go to Solution.
Thank you for your post. I have seen the following suggestion via the article below in regards to forcing a workflow into error state:
In regards to the second query you raised I have seen the suggestion made below:
I know this can only be done with custom code as well. There has been feature logged for this as well which can be viewed below:
This has discussed for future consideration but you may choose to include your vote on this as well.
I hope this helps.
I did also find a quick demo video on this as well in regards to how this can be achieved. This is in relation to the error notification email.
I have attached this to my response to the ticket.