Hi Aditya,
From the first screenshot it is clear HYP product load workflow which activated at 02:13 PM 09/06 was active till next day 8 AM that's why your next instance at 09:55 PM 09/06 error out with that error as you have set max parallel instance as 1 else abort option.
For the child workflow it is not clear from this screenshot what happened because its earlier instance i.e 02:13 PM which error out with this error. but this error means have restricted these jobs/WF to run 1 instance at a time else abort next instance if 1 is running.
so there should be instance for this child workflow was running at that time
Original Message:
Sent: Sep 10, 2024 06:15 AM
From: Aditya Simha S
Subject: Workflow was Blocked
Hi Arun,
The screenshots with start time and end time have been attached.
Thanks
Original Message:
Sent: Sep 10, 2024 05:22 AM
From: Arun Choudhari
Subject: Workflow was Blocked
Can you add start time and end time column in screenshot for all these screenshots.
Original Message:
Sent: Sep 10, 2024 01:47 AM
From: Ashmitha Ashmitha
Subject: Workflow was Blocked
Hello Team,
One of the workflow has been blocked in Automic. When we checked the parent execution of the workflow, we found an error "ENDED_JP_ABEND - not executed due to abnormal Workflow end". There was only one execution running at that particular time.
Parent Workflow Execution
In the child workflow also, we found the same error even though there is no parallel execution for the workflow "JOBP.E1_MDS_PRODUCT_CLOUD_BASE".
Then we checked for the child jobs running under child workflow, also had the similar error even though they didn't run parallelly at the same time.
Please help us in this issue.
Thanks,
Ashmitha