ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
CA WA DE (dSeries): External job did not complete and find home application job
Article ID: 186690
CA Workload Automation DE - Business Agents (dSeries)CA Workload Automation DEDSERIES- SERVERCA Workload Automation DE - System Agent (dSeries)CA Workload Automation DE - Scheduler (dSeries)
The external job stuck in EXTWAIT state. The home application job completed in time. The manager should have completed the external link job. What can be the cause of the external getting stuck?
If the external is stuck in EXTWAIT state, then it is likely It appears that the time limit may have been missed. In some are cases the external match may fail by a second due to epoch time generated by the JRE. The tracelog will show a message similar to the following about externals not found.
[2020-XX-XX_08:00:00.000] EXTERNAL match failed candidate=NEW_APPL.215.JOB1234, ext=JOB1234, candidateScheduled=1583445600000(Fri Mar 06 06:00:00 CST 2020), does not matchdesiredScheduledStart=1583445600001(Fri Mar 06 06:00:00 CST 2020), desiredScheduledLimit=1583532000001(Sat Mar 07 06:00:00 CST 2020) 2020XXXX 08:00:00.000 [externals] [INFO] DM.Appl.NEW_APPL.215: [2020-XX-XX_08:00:00.000] No Externals found waiting for =NEW_APPL.215.JOB1234
Release : 12.0, 12.x
Component : CA WORKLOAD AUTOMATION DE (DSERIES)
To avoid external time limit issue, increase of decrease the scheduled time limit by a minute or so. If the home application event is set trigger to come at 9 AM, then set the start time for external to 8:59 (see example below).