Hi everyone,
Can someone please help me understand why I can’t see what the workflow condition is doing, as shown in this photo
In my case, the condition doesn’t display the logic or expression next to the workflow step like it does in the video.
Is this a bug, or is there a setting I might have missed?
Thanks in advance for any help!
If you’ve manually renamed the workflow, then it won’t use the default name like the others
Thanks for the info, but just to clarify — I didn’t manually rename the workflow. Previously, when I added a group or action, it would automatically generate a default name that included the condition, which was very helpful.
Now, it seems that behavior has changed — the condition name is just missing, and I have to write it again manually.
Any idea why this is happening or if something has changed recently?
Appreciate your help!
If you delete the step and create a new one, does it work?
I haven’t tried deleting and recreating the step, because this issue is appearing in multiple places, and I’d prefer not to touch the workflow yet until I’m more familiar with the new workflow interface.
Also, I don’t think deleting and recreating should be the solution — my workflow is quite large, and that approach would be very time-consuming. At that point, it’s honestly easier to just rewrite the condition manually.
That said, I’m still curious — any idea why this is happening in the first place? It was working fine before, and I didn’t rename anything manually.
Appreciate your support!
now, if I’ve manually rewritten the condition name, and later I want to change the element, I have to delete and recreate the entire workflow step to get the updated condition to show automatically.
But before, when I changed the element, the condition description would automatically update, which was much faster and made it easier to test and troubleshoot elements quickly during bug fixing.
The current method really slows things down when debugging or testing different conditions in a large workflow.
Would love to know if this behavior is expected now, or if there’s a better way to handle this.
I don’t think this is the case. If you manually updated an action name, it would no longer use automatic naming.
Yes, if you haven’t manually overridden the behaviour. This is still what happens if you use the default names.
The behaviour you describe can be reproduced just by clicking on the action name and then clicking outside. Not funny.
You can solve it by deleting the action name completely. That will reset the automatic naming behaviour.
Video below
Wow, thank you! You just saved my life 
I was really frustrated having to rewrite the condition descriptions every time — I had no idea just deleting the action name would reset it.
Really appreciate your help!
Well, it should ideally update automatically — but at least you gave a great and super quick workaround to fix the issue. 
This topic was automatically closed after 14 days. New replies are no longer allowed.
