Hi all,
I’m trying to handle failures from the Send E-Mail smart service (e.g. network) in a more user-friendly way.
My goal is to display an interface showing the error and its corresponding resolution whenever the email fails, instead of having the process instance suspended.
Currently:
When the Send E-Mail smart service fails, the process model is suspended.
I attempted to:
Use a Timer Exception on the Send E-Mail node
Place the Send E-Mail node inside a subprocess and handle the exception from the parent model
However, both approaches do not work as expected because the subprocess itself becomes suspended when the Send E-Mail smart service fails.
Is there any supported way to:
Catch or handle Send E-Mail failures (e.g. network issues) without suspending the process, or
Route the flow to a failure interface after retries are exhausted?
Any guidance or recommended patterns would be greatly appreciated. Thanks in advance!
Discussion posts and replies are publicly visible
Process always suspends on failure -> there's no exception flow or continue on error option.Launch Send E-Mail in async subprocess. In the parent process, wait with a Timer Event, then query a process report on the subprocess to check if the output PV was updated. If the timeout expires before the PV updates, assume failure and route to the error interface.