• Public

Workflows

Skip Feed
  1. Pinned Post

    Max Katz (Okta)

    Edited September 18, 2026 at 5:15 PM

    👥 Our first Okta Workflows meetup in Chicago ⤵️

     

    📍 Chicago | Thur, Oct 15 @ 5:30 PM CT

    • A Peek into Okta Workflows Roadmap: AI Builder — Max Katz, Okta
    • Automate Breached Credentials Alerts in Okta Using Workflows — Karthick Chinthamani, Okta
    • Automating Manual App Access Requests with OIG and Workflows — Slava Primin (Workflows Community Member)

     

    📟 Register for Chicago: https://luma.com/2lzexp2k

    Expand Post

  1. VenkateshwarRaoG.85600 (Customer)

    Yesterday at 5:04 PM

    Hi All,

    need help

     

    As we have created workflow in preview for full aggregation (HR System to OKTA)

    we have tested and its working fine, Aggregation is taking Around 7hours.

    and

    we deployed same flows in Prod.

    now in Prod Full aggregation is taking 24hrs, and sometimes 18hours and some time 26hours.

     

    Preview and Prod have same user count 8,500.

    and there is no errors, as we built the table to record errors.

    My doubt is.

    is OKTA Prod has any limitations or capacity issues.

     

    Expand Post
    • 2 comments
    • 14 views
    1 of 2

    • VenkateshwarRaoG.85600 (Customer)

      Hi Max,

      Thank you for your response.

      As suggested, we reviewed the Okta Production System Log and Rate Limits dashboard during our full Oracle HCM aggregation runs. Please find our observations below:

      1. Same configurations: We are using the same Workflows logic and configurations in both Preview and Production, processing approximately 8,500 Oracle HCM workers.
      2. Significant execution time difference:
        • Preview: Approximately 7 hours.
        • Production (October 18–19): 13 hours 11 minutes.
        • Production (October 19–20): 25 hours 24 minutes.
      1. System Log verification: We checked the following events during the aggregation period and found no matching events:
        • system.org.rate_limit.warning
        • system.org.rate_limit.violation
        • core.concurrency.org.limit.violation
      1. Rate Limits dashboard: The dashboard showed zero violations, bursts, and warnings over the last seven days. The user API buckets also showed zero events in the available last-hour view.
      2. Our concern: Since we have not identified any API rate-limit violations, we suspect that Production Workflows shared-environment load, resource contention, or backend execution capacity may be contributing to the inconsistent performance.

      Could you please clarify:

      • Are there any Workflows processing capacity or concurrency limitations specific to Production?
      • Can Okta investigate backend throttling, execution queueing, or shared-environment resource contention?
      • Is it possible to increase or optimize the processing capacity allocated to our Production Workflows environment?

      We would appreciate your guidance, as the significant variation in execution time is affecting our Oracle HCM full aggregation process.

      Expand Post

  2. Max Katz (Okta)

    Edited September 18, 2026 at 5:15 PM

    👥 Our first Okta Workflows meetup in Chicago ⤵️

     

    📍 Chicago | Thur, Oct 15 @ 5:30 PM CT

    • A Peek into Okta Workflows Roadmap: AI Builder — Max Katz, Okta
    • Automate Breached Credentials Alerts in Okta Using Workflows — Karthick Chinthamani, Okta
    • Automating Manual App Access Requests with OIG and Workflows — Slava Primin (Workflows Community Member)

     

    📟 Register for Chicago: https://luma.com/2lzexp2k

    • 161 views
    Paul S. likes this.

  4. Max Katz (Okta)

    August 11, 2026 at 8:20 PM

    🎉 Okta Workflows Community Meetup — Oktane 2026

     

    Join us for our 4th Oktane meetup! Come hang out with the Okta Workflows community — including members of the product team — over drinks 🍻 and appetizers 🍔 at Virgil’s Real BBQ.

     

    🗓️ When: Wednesday, September 23 · 4:30–6:00 PM

    📍 Where: Virgil’s Real BBQ, Las Vegas (LINQ Promenade)

     

    Whether you’re a longtime Workflows user or just getting started, this is a great chance to meet the community and the product team.

     

    👉🏼 RSVP here: Okta Workflows Community Meetup, Oktane 2026 · Luma

     

    See you there!

    Expand Post
    • 72 views
    avshch and Paul S. like this.

  5. Max Katz (Okta)

    August 7, 2026 at 4:12 PM

    🎥 Automate Access Reviews Using Okta ITP, Workflows & OIG, Online Meetup (August 20, 2026) 

     

    The idea: instead of running access certifications on a quarterly schedule, you trigger a targeted review the moment a user’s risk profile actually spikes (e.g., session hijacking flagged by ITP).

     

    When

    • Thursday, August 20, 9:00 a.m. PT

    Speaker

    Things you will learn

    • Capture ITP risk signals (like session hijacking) with Workflows
    • Auto-trigger “Risky User Campaigns” in real time
    • Set up the Governance Analyzer for richer reviewer context (including unused license data)
    • Deploy the pre-built Workflows template into your own tenant

    Register

    Can’t attend live?

     

    Expand Post
    • 70 views
    avshch and Paul S. like this.

  6. IsaacB.81593 (Customer)

    July 18, 2026 at 11:11 PM

    I am building a set of workflows to maintain user attributes in a SaaS app (Cornerstone.) I want to update attributes that are not exposed to the OIN provisioning integration.

    I want to sync user.employeeNumber (and other attributes) to a fields in Cornerstone. I have the necessary API calls working.

    My intention is to sync attributes when a user is assigned to the app or if the user's account is updated and the update includes employeeNumber. (I have an event hook configured for the department update.) These updates are not time-critical.

    I'm concerned about 2 main things:

    1. The flow might execute before the OIN app provisions the user to Cornerstone. I can build in a delay and also verify that the user is in the app.
    2. The possibility of 1,000 assignments or updates in a short interval. In this case, I can have 1,000 flows, all running, all trying to update Cornerstone and hitting rate-limits/time-outs.

    What would be a good strategy for spreading out the hits against Cornerstone? I thought that instead of directly making API calls, I write each account that needs updating to a table, then schedule a job to read the row, wait, make the API call and delete the row.

    Any other recommendations?

    Thanks.

    Expand Post
    • 1 comment
    • 87 views

    • Max Katz (Okta)

      Hi @IsaacB.81593 (Customer)​,

       

      I think saving the users you need to update in a table and processing them later on a schedule is a viable solution. You would likely still want to check whether the user exists in Cornerstore. You can remove the user from the table after an update.

  7. Max Katz (Okta)

    June 11, 2026 at 11:23 AM

    🚀 Join us for a meetup: How to Automate Snowflake Access and Roles with Okta OIG and Workflows

     

    🗓️ June 24, 2026 @ 2 PM ET (11 AM PT)

    🎤 Purav Barot (Solutions Engineer, Okta)

     

    What you'll learn:

    • Go beyond SCIM connector limits and automate the full Snowflake user lifecycle
    • Run custom Snowflake commands directly from Okta Workflows
    • Auto-remove stale access when users change teams or leave — save licensing $ and tighten security

     

    Can't attend live? Register anyway for the recording + resources.

     

    🔗 Register

    Expand Post
    • 104 views
    Paul S. and Mihai N. like this.

  8. IsaacB.81593 (Customer)

    June 6, 2026 at 8:59 PM

    I would like to trigger a flow with an event hook when a user is created. I would like to only take action if a specified user profile attribute is populated, say department. Event hook documentation "Supported Filter Fields" section does not appear to list a method of testing for profile attributes (on a create. You can test this in a change.) Do I correctly assess that if I want to test for the profile value, I execute the flow and test the attribute in the flow? Thanks

    • 2 comments
    • 110 views
    1 of 2

    • Max Katz (Okta)

      Hi, I believe @MichaelM.97914 (Dexcom)​ is correct. Event hook filtering only supports the following fields:

       

      Screenshot 2026-06-07 at 9.38.50 PM 

      You would need to add logic at the beginning of a flow to check for the department.

      Expand Post

End of Feed
End of Feed
8 Chatter Feed Items

Group Details

Details