AutoSys Workload Automation

 View Only
  • 1.  Ignore the duplicate incidents when jobs are getting failed every 5min

    Posted Jun 03, 2024 06:45 AM

    Hi,

    I have a job is running every 5min.. so every time new incident is created for failure..I don't want duplicate incident untill I close open incident..is there any solution in autosys side.

    And another thing.

    My job is running every 5min.. if the job failed,next irritation should not be happen untill user take manual action ..is there any condition we can use in Jil attribute not to trigger next iteration when job fail.



  • 2.  RE: Ignore the duplicate incidents when jobs are getting failed every 5min

    Broadcom Employee
    Posted 25 days ago

    Hi,

    The only suggestion I can offer is if you have another job that runs on failure of this job and have it issue a sendevent to place it on hold.

    That would prevent the additional incidents and allow the user to resolve the problem and then take the job off hold.

    Regards,

    Mike




  • 3.  RE: Ignore the duplicate incidents when jobs are getting failed every 5min

    Broadcom Employee
    Posted 25 days ago

    Hi,

    In addition to Michael's response, another option to prevent the job from running again automatically following a failure would be to add a condition upon itself. For example:
    insert_job: joba
    condition: success(joba)

    If the job does not run successfully, it will not run again until manual action is taken. As the job is scheduled every 5mins this condition would not cause the job to spin constantly. 

    Just another option to consider.

    Thanks,
    Jon




  • 4.  RE: Ignore the duplicate incidents when jobs are getting failed every 5min

    Posted 24 days ago
    If I'm reading this correctly, you have joba and jobb. Once joba ends (successfully or not), you want jobb to run. However, you don't want joba running again if it fails until you fix it and you don't want jobb to trigger again after you rerun joba to success until after the next scheduled run of joba. Once both are in success, they should start at the next schedule with joba followed by jobb.

    If this is the case, I would create a box and put joba and jobb inside of it. I would also move the date conditions of running every 5 minutes from joba to the box itself. I would then add a condition of both joba and jobb going to success at the box level. On jobb, I'd add a condition of done for joba.

    What will happen is once joba ends (successfully or not), jobb runs only one time as it's in a box. Even if you force start joba again, job won't try to run. If both jobs run to success, the box starts at it's next time. However, if either of these jobs fail, the box will fail and won't run again until those jobs are rerun to success. Now if you don't care if jobb fails and you still want joba to run at it's next time as log as it's in success, change the condition: s(joba) & s(jobb) at the box level to condition: s(joba) & d(jobb) that way the box will keep running joba as long as it's in success.

    box_job
    condition: s(joba) & s(jobb) <-- Change s(job) to d(job) if you don't care if job fails and you want joba to continue on it's schedule.
    start_mins: 5,10,15 etc....

    joba
    box_name: box_job

    jobb
    box_name: box_job
    condition: d(joba)

    Leroy P. Zine
    Technology Engineering & Operations
    Bank of America
    403 E. Bidwell St, CA2-137-01-01, Folsom, CA 95630
    * 214-209-9601
    Leroy.Zine@bofa.com<mailto:leroy.zine@bofa.com>

    Contact Info: http://autosys.bankofamerica.com/contactus.html

    Our FAQ site : FAQ.pdf (bankofamerica.com)<http: autosys.bankofamerica.com/files/faq.pdf="">

    Job well done ? Tell someone! Use Global Recognition<https: fedsso.bankofamerica.com/idp/startsso.ping?partnerspid="fed.appreciatehub.com">!

    [cid:image001.png@01DAC949.118BC860]



    ----------------------------------------------------------------------
    This message, and any attachment(s), is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/electronic-disclaimer. If you are not the intended recipient, please delete this message. For more information about how Bank of America protects your privacy, including specific rights that may apply, please visit the following pages: https://business.bofa.com/en-us/content/global-privacy-notices.html (which includes global privacy notices) and https://www.bankofamerica.com/security-center/privacy-overview/ (which includes US State specific privacy notices such as the http://www.bankofamerica.com/ccpa-notice).