Okta Workflows Returns Error "Relative URL must include a leading '/'." When Streaming More Than 200 Records
Last Updated:
Workflows
Okta Classic Engine
Okta Identity Engine
Overview
When an Okta connection uses a custom domain, Okta Workflows generates a 400 error when streaming more than 200 records. Administrators must use the main Okta tenant URL to resolve this issue. Specifically, Okta generates the following error when attempting to stream more than 200 records using an Okta connector card:
"message": "Relative URL must include a leading '/'.",
"code": 400,
"description": "HTTP Request Error",
"steps": 34,
"operator": "!=",
"right-operand": "/",
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Workflows
- Custom Domain
Cause
The custom domain has been used to create the Okta connection as opposed to the default Okta tenant URL.
Solution
How is the relative URL error resolved when using a streaming action in Okta Workflows?
Update the existing Okta connection or create a new connection using the standard tenant domain to resolve the streaming error.
- Create a new Okta connection or update the existing connection using the main Okta tenant URL for the Domain field (for example,
<subdomain>.okta.com). - NOTE: Create a new connection if the existing connection with the custom domain is used for sending branded emails, as shown in Send an Okta Branded Activation Email via API Using a Custom Domain.
