Please share any images or screenshots, if relevant.
N.A.
Please share any other relevant files that may be required (for example, logs).
N.A.
Share all details about your problem, including any error messages you may have received.
I’m trying to find information regarding the order of which events are processed if multiple triggers match for a single identity. i.e., during an identity refresh task with process events enabled, an identity matches the identityselector for 5 different lifecycle events with 5 different workflows. which workflow runs first and which one runs last, or are they all concurrent and race conditions depend on which workflow steps are pending manual intervention/fully automated processing.
@Deon Could be wrong, but i think it’s based on the insertion order. One which is created first, will execute first. i tested this with two events having same conditions. Tried running it multiple times, one which i created first always gets executed first. i tried changing the names to make the 2nd one alphabetically before 1st, but it is still following the insertion order.
What is your usecase? If you can provide more details, we can see if there is any workaround.
Lifecycle Event evaluation is sequential, not concurrent. But the order is not guaranteed, so you should not assume any specific order while designing your life cycle events.
Workflows triggered by lifecycle events are launched asynchronously, so their execution may overlap.
Race conditions can occur, especially when:
multiple events fire in the same refresh
workflows modify the identity
approvals/manual steps delay one workflow while others continue
@Deon you will get these order in spt_audit_event table with account_name by created date if you look in db Or you can pull from audit in sailpoint. is this you are looking for ?
Thank you for all your suggestions. I have conducted a simple experiment (credit to @neel193) with 3 triggers and 3 workflows that print 1, 2, or 3, and have created lifecycle events for them in the order of 3, 1, 2.
They seem to execute in order of creation as shown below (lowest row executed first):
