GHL puts looping WF in Draft - send notification
complete
J
Jeff Mattus
When GHL puts a workflow in draft mode and blocks it from being published, please send a notification that this was done. Our client's depend on these to run flawlessly. When GHL puts a WF in draft mode without telling us, we look like idiots when our clients ask what happened.
Log In
Core Platform
complete
J
Jeff Mattus
Core Platform This is not completed. I just had this happen to a workflow and was not notified that the workflow was set to draft. This happened over 2 months ago and just found out about it now.
Core Platform
complete
Core Platform
Merged in a post:
Notify If Stuck on Workflow Step
J
Jacob Radcliffe
We need the system to notify us when there are loops identified or when a contact is stuck at a workflow step. We also need a toggle in the workflow to recheck steps on a configurable basis to catch contacts that are stuck. Right now, if a contact gets stuck they just stay there until you manually force them to the next step when it's an issue beyond our fixing.
Core Platform
Merged in a post:
I had a loop issue with a workflow
J
Jeff Mitchell
I had an issue with one of my client's account: The workflow was identified as having a loop issue. There was no way for me to reactivate this workflow once the issue was identified. Being able to identify the workflows affected by this loop was not easy.
The workflows that had the loop issue were put into draft mode and deactivated BUT the workflow folder showed all workflows as published... Until you clicked on each and every workflow automation and manually identified the workflows that gave me an error message, after the workflow builder loads.
Being able to get notified of a loop lockout would be extremely helpful, as well as easily identify the workflows and lastly being able to fix the error and reactivate it... I was unable to make a change to the workflow as the save button is not available... Again since it was such a pain point I feel the need to restate how I had to go into every single workflow that was on the account to even ID what workflow was disabled.
Now I have to go and check all of my clients accounts to ensure that this is not an issue any where else and this will take an extreme amount of time..... Dev team please help lol
R
Ryan O'Meallie
I had this same thing happen and it cost my client a 1-star review and a ton of nasty messages.... not easy to recoup that.