Sarah Paterson

Hi Sebastiaan, 

Thanks for pointing me in the direction of the error logs. I was getting a 422 error with the failure type "HTTP client call failed"

 

I clicked on one of the errors and saw the following under the Response section

{
  "error": "RecordInvalid",
  "description": "Record validation errors",
  "details": {
    "status": [
      {
        "description": "Status: closed prevents ticket update"
      }
    ]
  }
}

I took another look at my trigger and realized when I first set it up instead of using "Ticket is Updated" I used "Status has changed"

Am I correct that the issue was related to the trigger trying to update a closed ticket and failing?

 

 

So I've tried to set this up and it works for about a month, and then we get a message that there were too many failures and the extension was disabled. I thought maybe the trigger was firing too many times per ticket, so I set up the trigger using tags to only fire once per ticket. But when I made the update the extension disabled within an hour. 

Any ideas what may be causing it? Let me know if I need to provide any specific information.