This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Currently we are working on an issue where we are seeing an "inbound pipe" error during a scheduled workflow, terminating at the error.
However, the workflow doesn't officially complete; it simply terminates.
For the majority of workflows, when a workflow runs with errors, completing with errors, even if the workflow was unsuccessful, you can send an email via the events for that workflow, if the workflow completes with errors, to use as an alert or trigger, etc...
However this doesn't work when a workflow suddenly terminates with errors.
I'd like to see functionality added to all ow for an email event when a workflow terminates unexpectedly, without completing.
This way, I could set up a job to re-trigger the workflow if this happens.
This can occur when memory is swamped during the initial workflow.