What problem does it solve? Okta Workflows has non-obvious error handling rules: automatic card-level retry only fires on HTTP 429, custom retry codes require a List Construct workaround, nested If Error blocks are capped at three, and Return inside a Try block does not halt the parent flow. This Skill encodes those four quirks so you build correct retry and failure-propagation logic the first time. ## Core Features & Use Cases - Card-Level Retry Rules: Documents that retries fire only on HTTP 429 (and 504 in Connector Builder), with defaults of Retry 0 times, After 5 minutes, and Then options Halt Flow / Return Values / Run another Flow. - Custom Retry Status Codes: Shows how to retry on other HTTP errors using a List Construct card renamed to retry_codes, selected via "Specified errors" in the Raw Request card's Error Handling dialog. - Nesting and Propagation Limits: Covers the maximum of three nested If Error blocks and how to propagate hard failures from helper flows using Return Error / Return Error If outside the block. - Use Case: When a flow calling a rate-limited API intermittently fails with 503s, use this Skill to configure a Raw Request card with custom retry codes instead of relying on the default 429-only retry. ## Quick Start Ask how to make an Okta Workflows Raw Request card retry on HTTP 503 errors and propagate the failure to the parent flow if all retries fail.
