---
title: "Fix RaaS 'Key not found' (202) & 5-min timeout — Kiweely"
description: "Why Send Workday RaaS Request throws 'Key not found' when RaaS returns HTTP 202 Accepted with an empty body, or fails after 300 seconds with HTTP 406/500."
url: https://kiweely.com/guides/workday-orchestrate-raas-key-not-found-202-5-minute-timeout
---

# Why Send Workday RaaS Request fails with ‘Key not found’ (HTTP 202) or times out at 5 minutes

Send Workday RaaS Request defaults to a 300-second timeout unless raised in Orchestration Settings, causing HTTP 406 or 500 errors at 5 minutes. When a RaaS call in a loop returns HTTP 202 (still processing) with an empty body, is2xxStatusCode() passes and parsing crashes with ‘Key not found’.

-   **Checked** against Workday on November 6
-   Applies to **Workday Orchestrate**
-   4 min read
-   Published November 6
-   By Kiweely

## Why `Send Workday RaaS Request` times out at 5 minutes (300 seconds)

Workday’s documentation appears to state two conflicting time limits for Reports-as-a-Service (RaaS):

-   **Reference: Send Workday RaaS Request** states: *The RaaS report can take up to 1 hour to respond without timing out the orchestration. When the response is received, the overall orchestration timeout is reset.*
-   **Reference: WQL and RaaS Comparisons** states: *5-minute timeout for RaaS API calls from the Workday Cloud Platform (WCP) Gateway (`api.workday.com`).*

When you run a heavy **Send Workday RaaS Request** in an orchestration, the step frequently fails at **exactly 5 minutes (300 seconds)** with either an HTTP `406` or HTTP `500` response:

json

```
{"responseStatusCode": 406, "response": "406 : The result is taking too long to display in your browser."}
```

or:

json

```
{"responseStatusCode": 500, "response": "500 : Processing error occurred. java.lang.IllegalArgumentException: Account Request Type cannot be null"}
```

### Root cause: The 300-second default timeout in Orchestration Settings

Historically, the Workday reporting framework did not enforce the client-supplied timeout parameter on RaaS executions. Workday now strictly enforces the timeout configured in your orchestration’s **Settings** tab, which defaults to **300 seconds (5 minutes)**. When the 300-second timer expires while the report is still executing, the reporting framework cancels the query and returns HTTP `406` (`The result is taking too long to display in your browser`) or HTTP `500`.

### How to increase the RaaS execution timeout up to 1 hour

To allow a long-running **Send Workday RaaS Request** to run beyond 5 minutes (up to the 1-hour / 3,600-second ceiling):

1.  In **Orchestration Builder**, click the gear icon above the canvas to open **Orchestration Settings** (or inspect the **Settings** tab).
2.  Locate the timeout setting (which defaults to `300` seconds) and increase it to match your report’s required execution window (for example, `1800` for 30 minutes or `3600` for 60 minutes).
3.  Save and redeploy the orchestration. Note from **Reference: Send Workday RaaS Request** that when you view the logs for a long-running RaaS request, Orchestrate automatically appends `dsa` to the endpoint URL; this is normal long-running RaaS routing and can be safely ignored.

## Why `Send Workday RaaS Request` inside a loop fails with `"Key not found"` on HTTP `202`

A second failure mode occurs when you place a **Send Workday RaaS Request** step inside a **Loop** or **Batch Loop** (with a fallback error branch if the report fails) and one specific parameter batch takes ~10–11 minutes to run. Instead of triggering your fallback error handler, the RaaS step is marked **Succeeded** with a completely empty response payload, and the very next step (such as a JSON/XML parser, lookup, or **Create Values** step) crashes immediately with:

text

```
Key not found
```

### Root cause: HTTP `202 Accepted` is treated as a `2xx` success

When a RaaS request through the gateway is still processing when an intermediate gateway poll window expires, Workday can return **HTTP `202 Accepted`** (“still processing”) with an **empty response body**.

Because `202` falls within the `200`–`299` HTTP status code range:

1.  A retry policy whose **Successful Response Code Ranges** is set to `200`–`299` treats `202` as a completed, successful response (`isSuccess = true`) and does **not** retry or enter the step’s local error handler.
2.  Any branch condition checking `data.SendRaas.responseStatusCode.is2xxStatusCode()` evaluates to `true` because `.is2xxStatusCode()` (**Reference: Number Member Functions**) returns `true` for any integer from `200` to `299`.
3.  Execution skips your fallback branch and hands the empty `202` body directly to the next step, which throws `Key not found` when attempting to read the root report element or JSON key.

### How to prevent HTTP `202` empty payloads from crashing your loop

Apply three defenses whenever a RaaS report can run for several minutes:

#### 1\. Restrict HTTP retry policy success codes to `200`–`200` and retry on `202`

In **Orchestration Settings** -> **HTTP Retries**, configure the retry policy used by your RaaS or HTTP step so that only HTTP `200` (`200` to `200`) is considered a final success, and add a retry **Condition** for **Status Code** `202` with an exponential backoff interval.

#### 2\. Check `responseStatusCode.equals(200)` and non-empty body before parsing

Never rely solely on `.is2xxStatusCode()` before parsing a RaaS response that could return `202` or an empty dataset. In your **Branch on Conditions** or **Continue on Conditions** step, verify that the status code is specifically `200` and that the response payload has content:

javascript

```
data.SendWorkdayRaasRequest.responseStatusCode.equals(200).and(
  data.SendWorkdayRaasRequest.response.contentLength().greaterThan(0)
)
```

If you are extracting a JSON or XML key from a RaaS report that may legitimately return zero rows for a given prompt parameter (when Workday omits the root `Report_Entry` array on an empty JSON report), use the `WithDefault` extraction functions—such as `.arrayAtJsonPathWithDefault("$.Report_Entry", "[]".asJSON())` or `.stringAtXPathWithDefault("/wd:Report_Data/wd:Report_Entry/wd:Worker_ID", "")`—instead of `.objectAtJsonPath` or `.stringAtJsonPath`, which throw an exception when the key is absent.

#### 3\. Move `Send Workday RaaS Request` outside of loops

As a general rule, avoid calling **Send Workday RaaS Request** repeatedly inside a **Loop** or **Batch Loop**. A RaaS step inside a loop disables loop pipelining and multiplies report startup overhead by the number of iterations. Instead, run the RaaS report once before the loop (or use a paginated **Send Paged Workday REST Call** with WQL if you need partitioned extracts), and join or filter the records inside the orchestration using a **Join Loop** or **Batch Loop** with `Group` strategy.

## How to verify RaaS timeout and empty-payload handling in the tenant

1.  Open **Orchestration Settings**, verify that the timeout is raised above `300` seconds for long-running reports, and deploy the app.
2.  Run the orchestration with a parameter set that previously timed out at 5 minutes and confirm in **Orchestration Activity** that the **Send Workday RaaS Request** step runs past the 300-second mark and completes with `responseStatusCode = 200`.
3.  Test the orchestration with prompt parameters that return zero rows from the Custom Report and verify that your `contentLength().greaterThan(0)` and `WithDefault` guards prevent `Key not found` exceptions.

## Sources checked

-   [Reference: Send Workday RaaS Request](https://developer.workday.com/documentation/GUID-bd5c7437-7ad2-4917-8dfa-cf886aa22ff2)
-   [Reference: WQL and RaaS Comparisons](https://developer.workday.com/documentation/GUID-8f1d3acf-87ba-4de7-9dc5-84e3991be6a2-enHYPHENus)
-   [Define HTTP Retry Policies](https://developer.workday.com/documentation/GUID-d04cc763-a044-423f-b39e-1348dfd76a87)
-   [Reference: Number Member Functions](https://developer.workday.com/documentation/GUID-c654c1ed-228c-4855-a450-ebc2fb9a03f1)
-   [Reference: Orchestration Runtime Limits](https://developer.workday.com/documentation/GUID-b341f6f0-cd6f-4930-8bcb-723a03f64805)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Fixing ‘Fast forwarding to correct position’ and 45-minute timeouts in Orchestrate batchLoop A small RaaS step inside a Batch Loop does not reset the 45-minute process timer and disables pipelining. Passing a paged REST iterator directly into a checkpointing Batch Loop throws ‘Fast forwarding to correct position’. Stage pages in a Loop first, and chunk with Trigger Integration.](https://kiweely.com/guides/workday-orchestrate-batchloop-paginatedget-fast-forwarding-timeout)
-   [### Why Workday sub-orchestrations and BP orchestrations show Completed when an API call fails By default, Send Workday API Request sets isSuccess to true whenever Workday returns a response, even a SOAP fault or validation error. Use a custom HTTP retry policy, Continue on Conditions with isSoapFault(), or an Integration System orchestration with Add Integration Message to surface failures.](https://kiweely.com/guides/workday-orchestrate-sub-orchestration-completed-on-api-error)
-   [### Why SendWorkdayRaasRequest returns 401 Unauthorized or empty data via the cloud proxy Send Workday RaaS Request routes through the Workday Cloud Platform API Gateway (/raas/<Report\_Owner>/<Report\_Alias>). A 401 Unauthorized or empty payload occurs when the ISU/credential context, report owner path, or XML formatting (pretty-printed vs compact single-line) is misconfigured.](https://kiweely.com/guides/workday-orchestrate-sendworkdayraasrequest-401-cloud-proxy)
-   [### How do I debug a Workday Orchestrate orchestration that shows success but some steps failed? A run can look successful because an unsuccessful HTTP response is not a failure unless a retry policy defines a success range, and an error handler set to Conditional Outputs lets the run carry on. Read the run’s per-process stepsFailed, not the status.](https://kiweely.com/guides/orchestrate-errors)

### More guides on Orchestrate

[All 86 guides](https://kiweely.com/guides#orchestrate)

-   [Fixing ‘not a simple type launch parameter (Text, Number, Boolean, Date)’ on blank O4I launch parameters](https://kiweely.com/guides/workday-orchestrate-null-launch-parameter-not-simple-type)
-   [Storing and Migrating External Client CredStore OAuth Credentials and Masked Integration Attributes in Workday Orchestrate](https://kiweely.com/guides/workday-orchestrate-migrate-external-client-credstore-secrets)
-   [JSONPath Logical Filter Expressions and Wildcard XPaths in Workday Orchestrate](https://kiweely.com/guides/workday-orchestrate-jsonpath-logical-filters-xpath-wildcards)
-   [Preventing Duplicate Records on Orchestration Rerun and Concurrent Webhook Triggers in Workday](https://kiweely.com/guides/workday-orchestrate-idempotency-concurrent-webhooks-duplicates)
-   [Reading the HTTP Response Content-Type Header in Workday Orchestrate](https://kiweely.com/guides/workday-orchestrate-http-response-content-type-header)
-   [Transforming dynamic-key JSON to CSV and grouping flat CSV rows into nested JSON in Orchestrate](https://kiweely.com/guides/workday-orchestrate-dynamic-json-keys-to-csv-grouped-json)
-   [Custom CSV formatting in Workday Orchestrate: Windows CRLF line endings, title rows, and skipping preamble lines](https://kiweely.com/guides/workday-orchestrate-csv-crlf-title-row-skip-header-lines)
-   [Resolving ‘\[StepException\] requirement failed: Input lists must be of the same size’ in createReferenceList](https://kiweely.com/guides/workday-orchestrate-createreferencelist-input-lists-same-size)

### From the blog on Orchestrate

[All posts](https://kiweely.com/blog)

-   [How Kiweely Vine designs, builds, deploys, tests and monitors a Workday Orchestration for Integration](https://kiweely.com/blog/workday-orchestration-for-integration-with-kiweely)
-   [Why Workday Studio Remains Essential in an Orchestrate World](https://kiweely.com/blog/why-workday-studio-still-matters-with-orchestrate)
-   [Debugging Workday Extend apps and orchestrations in kiweely](https://kiweely.com/blog/debugging-workday-extend-apps-orchestrations-kiweely)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
