Ticket Automator - Service Request - Not Running Rule

Hello @Mike.T 

Can you share what your workflow looks like so we can better troubleshoot your issue? In my experience when a workflow is not being triggered it has to do with the action event and how it responds to the ticket creation state. Also another big factor is where the workflow is set in its order. If other workflows that are triggered by the same event are ahead of it and make changes to the ticket, that could be preventing this workflow from running.

Just some ideas, hope this helps

-Zach

Hey @Mike.T 

So this looks pretty standard, my guess is that it has to do with the conditional not being met correctly. If you’d like you can DM me here (if you are concerned about privacy) and send me a screenshot of the conditional opened up so I can see its contents, and also an example SR that is created with the activities tab expanded to see if the workflow is being triggered at all.

Thanks,

Zach

@JVDS, when the service request is raised, and you click the activities tab, does it show if the workflow was triggered at all? Also do you have any other workflow automators that run when a Service Request is raised that reside above this automator?

@JVDS no worries, I am sure we can figure out the issue. You can definitely have more than one workflow automator that uses the same trigger. It is best practice to try and group automations together in the same workflow if possible to declutter the amount of workflows you have but this is not necessary. The big thing is that if a workflow, that is triggered by “Service Request is raised” or any other trigger that matches your new one, resides above your new one, and changes the ticket so that it no longer meets the condition of your new one, it won’t apply the actions specified in your new automator. So try changing the order of the automators, or maybe disable the others, and test it out. See if that fixes the issue.

Here is some documentation - https://support.freshservice.com/support/solutions/folders/273935. You can send me a DM if you need some further help. I try and respond as quickly as I can lol :)

🎉  Great News!! When workflows fail, it is almost alway due to collisions with other workflows :) Take care!

Hey @Mike.T, 

I think a workflow automator is perfect for this scenario, as long as when you say “kick off other tasks” you mean create a task for that ticket.

Would look something like this:

Obviously this is just an example but what matters most is how you isolate the ticket so that it triggers the workflow. When it comes to email, it helps to identify the source, from email address, requester, or subject line. Things you know won’t change. Also if you choose subject line, in my experience use “Contains” and not “is”. Selecting “Is” is so limiting that it often won’t allow the workflow to be triggered. Just something I have learned :)

Hope this helps

-Zach

Can you change ticket.fields.from to request.fields Requester Email and see if that makes a difference. If you don’t see the workflow under the Activities page then it’s not being triggered. I would start by removing conditionals until the creation of the ticket triggers the workflow. This will help identify why it’s not running. Also place the workflow at the very top of the list of automators and see if that helps.

Ok this is extremely difficult to troubleshoot without seeing the workflow or testing in your instance. I would suggest reaching out to support@freshservice.com so that a tech can access your instance and make sure its functioning correctly. Sorry I couldn’t be more help Mike.