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

[Tim Deniston]

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? 

[michaelj_sherid]

@Tim Deniston I was mixing the peanut butter and jelly 🙂 It is the SFSF integration that has the # of retries, not the Workday integration. This simplifies things for you.

Regards,

Mike

[Tim Deniston]

Here is what I am working on so far. After digging through the Cancel UI action on the wf_context table, I don't think it's feasible to have a single UI action that will take care of this from the job tracker record. It might be possible, but it would require rewriting the Cancel UI action to make it work in the HR Integrations scope. 

So, instead, I decided to build some steps into the job tracker form using a UI macro that the user would follow. 

There are two sets of steps that could appear based on a query for active contexts running for this import:

Set 1 - Active wf_context record found for this import

Set 2 - No active wf_context record found for this import

I positioned this below all of the fields on the job tracker form. This will at least explicitly define the proper steps to follow and make it easier for an admin to get a WD integration back on track. 

Any other suggestions?