I may have missed the nuance here but I wanted to add to what others have said.
Instead of using S(JobA) or F(JobA) maybe use D(JobA) instead?
That will trigger when JobA is done, reaching a valid end state. This may give you what you need. Unfortunately have a job depend on success of itself only really works if that job isn't in a box, otherwise I would second the earlier recommendation on this. If this is a top-level object then that would work as well.
Best of luck!
Scott
________________________________
Your Personal Data: We may collect and process information about you that may be subject to data protection laws. For more information about how we use and disclose your personal data, how we protect your information, our legal basis to use your information, your rights and who you can contact, please refer to:
www.gs.com/privacy-notices<http: www.gs.com/privacy-notices="">
Original Message:
Sent: 6/27/2024 9:23:00 AM
From: Michael Woods
Subject: RE: How to set first success instance dependency for another job have multiple schedule
Hi,
It sounds like JobB may not be dependent on JobA if it can run on success or failure. Could it just have the same starting condition as JobA so that it only runs once?
Mike
Original Message:
Sent: May 28, 2024 01:07 PM
From: Inaganti Ramesh
Subject: How to set first success instance dependency for another job have multiple schedule
How to set first success instance dependency for another job have multiple schedule.
JobA
JobB have below condition
Condition: S(JobA) OR F(JobA)
If jobA fail , JobB will trigger
If JobA fail and took manul action then it got success( 2nd attempt ). JobB triggered again 2nd time.
I don't want JobB run second time when JobA take manual action for success(2nd instance)
Is there any way condition look for only first instance of jobA status ? Or like 2nd instance of job status
</http:>