JOb failure with Message connection has already been closed

[Kaushik1]

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?

[rushikeshvartak]

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

[Kaushik1]

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.