Short and handy Okta Workflows tips and tricks. Read the full series.
When a system invokes a flow via an API endpoint, it is a good practice to close the connection to avoid a timeout error.
Because the API endpoint closes its connection to a client at 60 seconds, a flow fails if the operation takes any longer than that. Some HTTP clients that invoke an API endpoint flow could have an even lower timeout than the default API timeout. For example, Okta inline hooks have a default timeout of 3 seconds.
For example, use the API Connector-Close card to close the connection.
Learn more about leveraging the API endpoint efficiently:
- Structure flows asynchronously.
- Place the API Connector Close Card first in a flow.
- Keep synchronous flows simple and fast.
Okta Workflows resources
🚀 New to Okta Workflows? The How to Get Started with Okta Workflows page outlines straightforward steps to get started.
📺 Like learning from videos? Watch Okta Workflows videos.
❓Have a question? Ask during community office hours, post on the community forum, or email me.
🙋🏻♀️ Want to learn from the community? Join the #okta-workflows channel on the Mac Admins Slack.
📖 Want to learn more about Okta and automation? Take the Okta Workflows training on Okta Learning.
Leave a Reply