Preventing an Endless Loop | The place for Zendesk users to come together and share
Skip to main content
Michael
Michael
User Group Leader
April 28, 2025
Solved

Preventing an Endless Loop

  • April 28, 2025
  • 1 reply
  • 99 views

In playing around with Action Builder, I got myself into an endless loop on pure accident.

 

I created a flow that is triggered on Ticket Create, it makes a webservice call and then updates the ticket with a comment. 

 

I created a 2nd flow that is triggered from Updating the subject line, it creates a new ticket.

 

I made an update to a ticket and changed the subject line, my flow ran and it correctly created a new ticket. It kept firing multiple times until I deactivated the flows. 

 

My questions is, is there any safeguards or way to protect against a process running away? Additionally is there any logging like webhooks have?

 

 

      Best answer by Zach22

      Hi Michael, the best way to prevent an endless loop between multiple action flows is to add some value to the ticket and then reference that value in a condition as a filter in your other action flow. However, I recognise that we currently don't properly support conditions on ticket tags or using custom ticket fields which may make that not a practical suggestion right now. We're actively working on both of those items and expect to release those improvements over the next few months.  

       

      At the moment we do, however, have some rate limiting in place and internal monitoring to prevent things from getting too out of control. In terms of logging, you can find logs for all your action flow executions on the Integration logs page in Admin Center. 

      1 reply

      Zach22
      Zach22EmployeeAnswer
      Employee
      April 30, 2025

      Hi Michael, the best way to prevent an endless loop between multiple action flows is to add some value to the ticket and then reference that value in a condition as a filter in your other action flow. However, I recognise that we currently don't properly support conditions on ticket tags or using custom ticket fields which may make that not a practical suggestion right now. We're actively working on both of those items and expect to release those improvements over the next few months.  

       

      At the moment we do, however, have some rate limiting in place and internal monitoring to prevent things from getting too out of control. In terms of logging, you can find logs for all your action flow executions on the Integration logs page in Admin Center. 

      Terms & ConditionsAccessibility statement