We are delighted to share our new EIC Delivery Methodology for efficiently managing Saviynt Implementations and delivering quick time to value. CLICK HERE.

JOb failure with Message connection has already been closed

Kaushik1
New Contributor
New Contributor

We have a custom query job which is used to update some attribute of accounts present in one endpoint after validating the value of account present in other endpoint.  It takes 4-5 hours and then fails with error 'connection has already been closed'. Is there any way to fix this error?

2 REPLIES 2

rushikeshvartak
All-Star
All-Star

You need to optimize the custom query considering indexes on table. Here 4-5 hours too huge time that your query taking time. 


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Hi @rushikeshvartak ,

 

The query can longer be optimized, we tried applying various filters as well but that too didn't help. This was checked with saviynt for ticket as well where they confirmed the query can not be more optimized. Hence, we need to know if there is an alternate way to make it work.