Mid-Server 'Did not get a response', how to retry?

[bbarnard]

I'm using the mid server to execute a scheduled data import via JDBC. I've set up a scheduled job to do this and most of the time it works fine, however about once a day I receive a 'Did not get a response from the MID server after waiting for 310 seconds' when the job tries to run and if this happens my import fails. Then the next time it runs it works.

I would like to setup a retry on my job so that if it fails I can have it retry n times. Is there a way to do this?


Thanks,
Bryan

[john_andersen]

Try starting with this documentation:
http://wiki.service-now.com/index.php?title=ECC_Queue_Retry_Policy

I think it is what you are looking for.

[bbarnard]

Thanks for the info John, reading the wiki article it seems like this would work if I was receiving an error message from the MID server as an input to the ECC Queue, but in the case where no response is received there isn't criteria by which the retry policy could determine if it should retry.

I think I may be able to use the 'Completion Code' of the Progress Worker that gets created for this Scheduled Import to determine if it failed, since when no response is received the corresponding Progress Workers' completion code is set to Error. If I can find the Progress Worker that is associated with this instance of my scheduled import and evaluate the completion code I may be able to determine if there was an error and re-run the scheduled import. I'll try using the post-import script to implement this.

-Bryan