Automic Workload Automation

 View Only
  • 1.  Workflow was Blocked

    Posted 23 days ago

    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

    image

    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".

    image

    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.

    image

    Please help us in this issue.

    Thanks,
    Ashmitha



  • 2.  RE: Workflow was Blocked

    Posted 23 days ago

    Hi Ashmitha,

    Do you have sync object defined in the job? If yes, what is the state of Sync Object?

    Regards,

    Eshwar



    ------------------------------
    Regards,

    Eshwar
    ------------------------------



  • 3.  RE: Workflow was Blocked

    Posted 23 days ago

    Hi Eshwar,

    There is no sync object in the job.

    Thanks,

    Aditya Simha S




  • 4.  RE: Workflow was Blocked

    Posted 23 days ago

    Can you add start time and end time column in screenshot for all these screenshots.




  • 5.  RE: Workflow was Blocked

    Posted 23 days ago

    Hi Arun,

    The screenshots with start time and end time have been attached.

    Thanks




  • 6.  RE: Workflow was Blocked

    Posted 22 days ago

    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