Proper way to end a stalled Workday HR Integration/job tracker

Tim Deniston
Mega Sage
Mega Sage

About once or twice each month, we have a Workday data import hang (due to Workday maintenance). When this happens, the job tracker that shows the status of the running Workday import continues to stay active and appears to continue running. There are no mechanisms to end the current import, but in order to get it back on track, we need to end the current job and kick off a new one. I have tried a couple methods in the past, and until recently (not sure what changed), I could enter a date in the 'Job ended at' field, set the 'State' to "Failed", add a note in the 'Error message' field, and save the job tracker. After that I would delete the HR Integrations Service Job Trackers records from the related list on the job tracker. If that wasn't done, the next import would use the same import set tables, which would sometimes mean that double the number of records would be processed on the next successful run. Then to get an import going again, I execute the regular scheduled job and hopefully everything goes OK. Lately, this has not been working correctly and we end up with another hung integration. 

So, I'm challenging the community... what is the correct way to handle this? How do we properly end a job tracker and get the integration back on track? How do you handle situations like this? 

6 REPLIES 6

michaelj_sherid
ServiceNow Employee
ServiceNow Employee

@Tim Deniston Just deleting the job tracker record will not terminate the process. You will have to go to the Workflow Contexts and terminate it there. You will see it being executed by the HR Integrations process. This will ensure that the process has ended.

Regards,

Mike

Great! That gets me closer to a solution. What I am hoping to do is create a UI action on the job tracker record that will end an import in one step. Leveraging the functionality from the "Cancel" UI action on the wf_context table will help. 

I assume that using the Cancel UI action by itself will not terminate the job tracker. Is that right? 

@Tim Deniston That is correct. Keep in mind that there is the retry option as part of the integration so you may not want to terminate it before it went through the # of times you want to retry. This may complicate what you are trying to do.

Regards,

Mike

I'm not familiar with the retry option. I can't find any info about this on the Docs site. Where is that configured? 

When the import hangs, it is usually identified the following day. I have a scheduled report that sends out daily if a job tracker was created before "today" and the State is Running, so I would guess that any retry attempts have already occurred.