Automic Workload Automation

Can we meet this requirement in Automation engine 11.2.4 , We have put one oracle EBS job in the workflow and put it in the schedule object and this job is scheduled weekly Monday @ 05:00 AM GMT . Now the requirement is if this job gets aborted or failed on Monday  it should gets Auto trigger  again on Tuesday at the same time and again if it gets failed then it gets again started on Wednesday at same time and then finally run on next week as per schedule time.

You could create a workflow that runs every Tuesday at the same time.  In this workflow you add your job, and add a precondition rule in the workflow task properties.  This precondition rule would use the "Check History" feature to check for weather or not the job ran successfully in the previous 24 hours.  It can then decide to either RUN TASK or SKIP TASK based upon the outcome of the condition.

If there is a possibility that the same job could run as part of other business processes and therefore "Check History" might result in false hits, then you would need to use a static variable object where you store the state of the Monday run at end of job, and check this variable on Tuesday.

Another options is to use a sync object that sets the sync status to 'Process' if the job abends or 'Skip' the the job is successful.  Schedule this as normal to run Mon -  Wed.
In addition you would need a script setup to reset the sync back to 'Process' before Monday to ensure Monday run would always occur.

Hi Pete,
Thanks very much for your answer. Can you be able to help with screenshots ?

I will assume you want the precondition rule solution, because it is simpler to implement.  (precondition rules are set in the task properties of a workflow task, so you may need to add a workflow object to run your job if the job currently runs by itself.)

Here is an example precondition rule from our systems that checks for the completion of a specific object anytime in the previous 4 hours.  If it has completed, the task is skipped.  If it has not completed, then the task is executed.  (In this use case, the step sends an email alarm to appropriate staff that a critical business process is late.)   Your solution would be done similar to this.

And I strongly recommend running tests in a non production client.

https://us.v-cdn.net/5019921/uploads/editor/8p/zy3t9t1eiyea.png" width="515">