Skip to main content
New Idea

Failing Workflow Automations Should Be Easier To Identify

Related products:Freshservice
  • January 17, 2025
  • 2 replies
  • 75 views

Forum|alt.badge.img+11

It is common for a change to take place elsewhere in Freshservice which results in an Active related Workflow Automation breaking.

The more Workspaces, Workflows and Administrators you have, the more difficult this is to manage.

Many of these Workflows would not necessarily, even when working, log anything in the Execution Log, so you may be unaware that it is even broken in the first place.

An issue you may face, as a result, is all subsequent Workflows will also fail to trigger.

So, with that said, I suggest the following improvements:

  • Set the label and/or toggle colours to Red if the Workflow is failing:
  • Highlight the edge or change the text within a Workflow node to Red if it is incomplete or causing issues: 
  • Email (at least) the person who last modified the Workflow to advise them that their Workflow is failing to trigger

     

2 replies

Forum|alt.badge.img+1

we are having the same issue logs seems to be fine but workflow has an error in a node 

 


kpatterson
Top Contributor ⭐
Forum|alt.badge.img+8
  • Top Contributor ⭐
  • February 5, 2025

100% this!  As our workflows have built up to almost triple digits, needing to open and traverse each workflow when a change is made to a single form field is ridiculous.  There HAS to be a better option!  Even careful labeling to associate workflows to specific forms only does so much to minimize this extra effort.