Bridge Workflow Error Notification

jessica.smith

I'd like the option to detect errors and trigger a notification to myself when a Bridge Workflow stops.

This would be particularly useful when running a child workflow as the entire parent and all subsequent children workflows will stop running if an error occurs. It would be nice to know that I need to retrigger my parent workflow without having to constantly manually check the status.

Filip Jevtic

Would it be possible to have "Stopped By Error" E-mail sent to the WorkFlow creator?

When flow was not competed, and status "Stopped" appears in Run Log - can we set that as trigger for E-mail to be sent to the flow creator that will inform him that the flow has failed?

Peter Nawrocki

In scenarios involving numerous workflows and workspaces, the current Bridge Workflow system in Smartsheet presents a challenge. Specifically, when a workflow stops due to an error, this not only affects the immediate workflow but also has a cascading effect on related workflows. This is particularly problematic in complex systems where multiple workflows are interdependent.

The absence of an automated notification system to alert users when such stoppages occur results in the need for continuous manual monitoring. This requirement is particularly taxing in large-scale implementations, where keeping track of each workflow's status becomes a daunting task.

An enhancement in Smartsheet that addresses this issue, providing more robust monitoring capabilities for Bridge Workflows, would be of great value. It would not only improve the efficiency of managing large workflow systems but also significantly reduce the risk of unnoticed workflow interruptions.

Such a feature would be a great addition to Smartsheet, enhancing its utility and reliability for users managing extensive workflow systems.

Peter

Samuel Mueller

It would be nice to be able to send a notification to the bridge admins if a notification fails, or even better sent to a specific email address. For example, one of my workflows failed with this random error and I didn't know about it until someone told me something wasn't working.

Zeb Loewenstein

@jessica.smith @Samuel Mueller - a workaround for this would be to:
1. Set up an independent macro which runs independently of your desired API with the trigger being time-based so it operates automatically without any human action (e.g. every 15 min). Have this search against criteria in the affected sheet(s) which would inform you something didn't process. If the criteria is complex, then have this be driven by column-based formula.

E.g. in mine I compare UTC time of row against current UTC where if delta is > 30 min, to update a flag on the row.

2. The flag on the row would then trigger either automation via email or public Teams channel.