
3dl5q (3dl5q) asked a question.
Hi everyone!
I'm currently stuck trying to build an exit condition into my workflow.
The goal is to get device scoped to a static group in Jamf Pro so a policy can execute on the device. And then to use an exit event that I define from Okta System Log to trigger automation to remove that device/s from the static group. The events to look for would need to only be AFTER the trigger, for success signins to either Okta OIDC App ID *1 OR Okta OIDC App ID *2.
For some context the below is already done and confirmed working:
- Triggers when an Okta user's password is reset.
- Grabs the Okta username.
- Connects to Jamf Pro API to find all devices associated with the Okta username.
- Use List - For Each to process each individual device ID into just the device ID number i.e "22, 23" and then process each one with an Add to Static Group - Jamf card.
The above works fine but the tricky part is the exit condition. So for my logic is as follows:
- Use a table to track UUID, Username, Device ID/s, PasswordChangedTimestamp, CompletionTimestamp, Status.
- Right after the trigger use the Time - Now card to anchor the beginning PasswordChangedTimestamp
I'm having a bit of an issue putting together things from here. I have a "List - For Each" card processing deviceIDs and would technically need to overlap its function to push out those deviceIDs into the sheet. Those devices would then need to be tracked in a way that if they trigger again those UUIDs should be separate from the previously so there's no overlap. As well as automation needs to be able to handle tracking multiple instances at once i.e other devices with failover criteria if running for 3 days then it should end the workflow and clear out the entries from the sheet. That same clearing should happen at the end of successful exit.

Hello @3dl5q (3dl5q) Thank you for posting on our Community page!
A few things we could add here:
For UUID tracking you would need to manage by checking (preferably) external to tables.
At this time there is no auto-cancel for flows.
You could could add clear table to the start of the PARENT flow.
While we'll do our best to answer all of your questions here, we do recommend further investigating this with your Okta account team.
Thank you for reaching out to our Community and have a great day!
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Collect them all. Learn a new skill and earn a new Okta Learning badge.
I've added some screenshots for additional context