Queued Status

I’ve noticed some times where groovy scripts get hung in Queued status and it’s happening more and more lately.  The Admin manual doesn’t say much about it, so I’m working if anyone has any more experience about what causes a script to be Queued and not immediately processed. 

I’ve seen it where a script can be queued for processing but then the same script runs minutes later after a different user triggers it – and then the original script stays queued for days.  

Does anyone know how I should handle Queued groovy scripts?

No Files Were Attached
Matt Paulhus Agile Expert Asked on January 10, 2018 in Other APIs.
Add Comment
2 Answer(s)

Matt, do you periodically refresh the system… restart the processes, or any periodic system maintenance?  This seems to help reduce these types of issues.

Patrick Lawrence Agile Angel Answered on April 10, 2018.
Add Comment

Thanks – yes, I found that scripts in Queued status end up working their way out after application refreshes (and I currently have no scripts in “Queued” status).

Matt Paulhus Agile Expert Answered on April 10, 2018.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.