Reason why Projects are Stuck in a "Queued" State for Publishing


You would like to know the reason for why published projects are stuck in the queued state.


Aggressive multithreading depletes the DB connections of the connection pool causing jobs to fail

Please contact EPM Support to get the issue resolved

  • Our teams will reset the status of failing jobs to be re-picked for execution restart the timer service and repeat this multiple times until the jobs queue is empty


Please escalate the issue to the SaaS Ops team who will perform the next steps (reset status, restart service, until the job queue is empty)




Please sign in to leave a comment.