We have installed a fresh copy of AE 12.1.1 HF3 in our new QA box. We have noticed that when we monitor our schedules, the status of a few tasks of type JOBS and Scripts are always showing READY for GENERATION. When we check the executions of the same tasks then they show the correct status. Other tasks like JOBP and Events show the correct status in the Schedule Monitor. Issue can be seen in Java UI and AWI.
This issue was present in 12.1.1 HF2 also and now is present in HF3 also. Anyone else facing the same issue?
Hi Kumar. I'm seeing this in V12.1.1 HF4 too.
Did anyone of you open a support ticket for that?
I just have - 01079124
Cheers for that!
And fwiw, all forum participants outside of your own organisation are prohibited from seeing your support cases, so sadly, can't do anything with that link.
Same here (I guess ... if that's what you meant):
The JOBS in the scheduler says "Ready for generation", while the JOBS with the exact same RunID is ENDED_OK. I assume this is a simple logic/display issue where the JSCH monitor shows the previous run id, but the state of the next upcoming job instance.
Automic Web Interface 12.1.1.HF3-dev-feature-12.1.1-HF.3-70410
Automation Engine API 12.1.1+build.9812
This issue has been confirmed as a product defect.Root Cause: The monitor of a schedule object is not updated during the execution of a task. Task state is set to "ready for generation" but not updated any more afterwards if the state of the sub-task is changed.
Solution: Update to a fixed version listed below or a newer version if available
Workaround: Change status manually
Fix Version(s):AE Server and InitialdataAutomation Engine 12.2.0 - Planned release date: 2018-06-19Automation Engine 12.1.2 - Planned release date: 2018-05-21Automation Engine 12.0.5 - Planned release date: 2018-05-07
KE detail: Scheduler does not show correct status of started Task in AWI and Java GUI
Thanks for the update.
Unless I missunderstand, this raises two questions with me:
Exactly! The workaround can be safely ignored. The only workaround is to check the actual executions of the task showing “Ready for Generation” status, because we know that the affected tasks are getting triggered.
-> Let me fix my statement as "This issue has been confirmed as a product defect." as I can't share more information on this. I'm afraid I don't have enough knowledge and also privilege to answer this question.
-> You are right. As this is a Display issue, manually change status does not take effect to the JSCH monitoring.
I will contact the KE owner to have this correct.