---
title: "Fix SendWorkdayRaasRequest 401 & empty data — Kiweely"
description: "Troubleshooting SendWorkdayRaasRequest 401 Unauthorized and empty XML payloads when calling api.us.wcp.workday.com/raas vs the direct tenant RaaS URL."
url: https://kiweely.com/guides/workday-orchestrate-sendworkdayraasrequest-401-cloud-proxy
---

# 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.

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

## How `Send Workday RaaS Request` routes calls differently from the direct tenant URL

When you test a custom report enabled as a web service (RaaS) outside of Workday Orchestrate, you typically call the tenanted Workday Web Services host directly using Basic Authentication or OAuth:

text

```
GET https://<workday-host>.workday.com/ccx/service/customreport2/<tenant>/<Report_Owner>/<Report_Name>?format=simplexml
```

Inside an orchestration, however, the **Send Workday RaaS Request** component does not call `/ccx/service/customreport2/...` directly. Instead, it prepopulates the regional Workday Cloud Platform API Gateway base URL and constructs a cloud-proxied RaaS request:

text

```
GET https://api.us.wcp.workday.com/raas/<Report_Owner>/<Report_Name>?format=simplexml
```

Because **Send Workday RaaS Request** routes through the WCP API Gateway using the orchestration’s execution credential (`_DEFAULT_WORKDAY_CREDENTIAL` or a configured ISU credential), developers often run into a puzzling mismatch after reassigning an Integration System User (ISU) or editing expression strings: the direct `/ccx/service/customreport2/` URL returns data when tested in a REST client with the ISU’s username and password, while **Send Workday RaaS Request** returns `{"error":"Unauthorized"}` (HTTP `401`) or silently outputs an empty payload at runtime.

## Cause 1: Calling `api.us.wcp.workday.com/raas/` directly with Basic Auth vs WCP OAuth

If you copy the `https://api.us.wcp.workday.com/raas/<Report_Owner>/<Report_Name>` URL from the **Integration Event** trace and call it from an external HTTP client using the ISU’s Basic Authentication username and password, the WCP API Gateway will always return HTTP `401` (`{"error":"Unauthorized"}`).

The WCP API Gateway (`api.us.wcp.workday.com` / `api.workday.com`) only accepts Workday Cloud Platform OAuth 2.0 bearer credentials issued for the tenant, whereas the direct `/ccx/service/customreport2/` endpoint accepts tenanted Basic Auth. To test the exact authentication context that **Send Workday RaaS Request** uses at runtime, use **Debug Step** inside **Orchestration Builder** connected to your tenant rather than calling `api.us.wcp.workday.com` with Basic Auth.

## Cause 2: Report Owner vs Run-As ISU mismatch after an ISU change

In the **Send Workday RaaS Request** path expression (`<Report_Owner>/<Report_Name>`), the first path segment is always the **Report Owner’s Workday username**, *not* the username of the currently executing ISU.

When a team creates a new Integration System User (`ISU_Integration_New`) to replace an older user (`ISU_Integration_Old`), three configurations must stay aligned:

| Configuration Item | What to Check in the Tenant |
| --- | --- |
|  **1\. RaaS URL Path Segment** | Run **View URLs** on the Custom Report’s related actions menu (**Web Service** -> **View URLs**). The path in **Send Workday RaaS Request** must use `<Report_Owner>/<Report_Name>`. If the report is still owned by `ISU_Integration_Old` (and was not transferred to `ISU_Integration_New`), changing the path prefix to `ISU_Integration_New/<Report_Name>` causes the gateway call to fail. |
|  **2\. Report Sharing with the New ISU** | If `ISU_Integration_Old` still owns the report while `ISU_Integration_New` is the **Run As** user on the Integration System, edit the Custom Report definition and verify under the **Share** tab that `ISU_Integration_New` (or its **Integration System Security Group**) is explicitly listed as an authorized user able to run the report. |
|  **3\. App & Integration System ISU Assignment** | Verify both the Integration System’s **Workday Account** (**Run As** user) and any named ISU credential configured on the **Credentials** tab in **Orchestration Settings** (**Assign Integration System Users to an App**). If the **Send Workday RaaS Request** step’s **General** tab selects a named ISU credential that still points to a deactivated or unassigned ISU instead of **Default Workday API Credential**, the WCP proxy rejects the call with `401 Unauthorized`. |

Do not replace **Send Workday RaaS Request** with a generic **Send HTTP Request** pointing to the direct `customreport2` URL: **Send Workday RaaS Request** automatically manages tenant routing across promotion lifecycles and resets the orchestration timeout when long-running reports complete.

## Cause 3: Multi-line or pretty-printed formatting in the path or downstream XML

A subtle issue in **Send Workday RaaS Request** occurs when the step builds cleanly at design time, the ISU has full report and domain permissions, and yet the step returns empty data or fails at runtime:

-   **Single-line path expression:** In the **Send Workday RaaS Request** namespace/path field alongside the prepopulated `GET` address, the expression must evaluate to a compact, single-line string (`"ISU_Owner/Worker_Audit_Report"` or `intsys.stringAttributeValue("Raas_Path")` with no leading slash, trailing whitespace, or embedded line breaks).
-   **Compact XML/JSON output handling:** When parsing or transforming the RaaS payload downstream, ensure the payload is processed in compact single-line format rather than relying on pretty-printed (indented) multi-line XML assumptions. Note also from **Reference: Send Workday RaaS Request** that the **Content Type** dropdown on the **General** tab (`application/xml` or `application/json`) only tells Orchestrate how to type the step’s output—it does *not* tell Workday which format to return. You must explicitly add a query parameter named `format` on the **Query Parameters** tab (set to `simplexml`, `xml`, or `json`) so the RaaS response format matches the **Content Type** selected on the **General** tab.

text

```
General Tab -> Content Type: application/xml
Query Parameters Tab -> key: format | value: "simplexml"
```

If **Content Type** is set to `application/json` while `format` on the **Query Parameters** tab is omitted (defaulting RaaS to XML) or mismatched, downstream JSONPath or XPath expressions will fail or return empty results.

## How to verify `Send Workday RaaS Request` in the tenant

1.  In the Workday tenant, open the Custom Report, select **Web Service** -> **View URLs**, and copy the exact `<Report_Owner>/<Report_Name>` segment.
2.  In **Orchestration Builder**, verify that the **Send Workday RaaS Request** path contains `<Report_Owner>/<Report_Name>` on a single line with no leading `/`, that **Authentication** on the **General** tab uses **Default Workday API Credential** (or your active assigned ISU), and that the **Query Parameters** tab sets `format` to match the **General** tab’s **Content Type**.
3.  Select the **Send Workday RaaS Request** step, click **Debug Step** against your connected tenant, and verify in **Debug Outputs** that `responseStatusCode` is `200` and `response` contains the populated report rows.

## Sources checked

-   [Reference: Send Workday RaaS Request](https://developer.workday.com/documentation/GUID-bd5c7437-7ad2-4917-8dfa-cf886aa22ff2)
-   [Concept: Reports-as-a-Service (RaaS)](https://developer.workday.com/documentation/hto1529968349582)
-   [Concept: Accessing RaaS Output](https://developer.workday.com/documentation/fdy1570549197818)
-   [Assign Integration System Users to an App](https://developer.workday.com/documentation/GUID-1bb7f6e1-e5e7-4cc4-8e35-6791062c23fa)
-   [Create Orchestration Credentials](https://developer.workday.com/documentation/GUID-d93db6e9-f07a-4e89-9ad0-2070f54c3286)

## Related guides

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

-   [### 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’.](https://kiweely.com/guides/workday-orchestrate-raas-key-not-found-202-5-minute-timeout)
-   [### 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)
-   [### Logging in Workday Orchestrate: Log, Log to File, Add Integration Message and verbose logging The Log step writes to the app logs on the Developer Site, kept 30 days. Add Integration Message writes to the integration event in the tenant. Log to File builds a named CSV log you attach with Store Document. Verbose logging is a time-limited REST switch for troubleshooting.](https://kiweely.com/guides/workday-orchestrate-logging)
-   [### 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)

-   [Reusing and versioning sub-orchestrations across Workday Extend and O4I apps](https://kiweely.com/guides/workday-orchestrate-reuse-sub-orchestrations-across-apps)
-   [Picking up SFTP files from subfolders and reading IDs from PDF filenames in Orchestrate](https://kiweely.com/guides/workday-orchestrate-sftp-subfolders-pdf-files)
-   [Sending email from Orchestrate: the Connect sendMessage API and email connectors](https://kiweely.com/guides/workday-orchestrate-send-email)
-   [How to keep large Workday Orchestrate loads inside the runtime limits: templates, checkpoints, batches and child runs](https://kiweely.com/guides/workday-orchestrate-runtime-limit-large-loads)
-   [How to rebuild an XSLT transformation in Workday Orchestrate](https://kiweely.com/guides/workday-orchestrate-replace-xslt)
-   [RaaS calls in Orchestrate: namespaces, unexpected character errors, 401s and empty reports](https://kiweely.com/guides/workday-orchestrate-raas-errors)
-   [How to process a CSV file in Orchestrate for Integrations, from Document Retrieval to the output file](https://kiweely.com/guides/workday-orchestrate-process-csv-file)
-   [Loading and reading Prism Analytics tables from a Workday orchestration](https://kiweely.com/guides/workday-orchestrate-prism-datasets)

### From the blog on Orchestrate

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

-   [Kiweely Roots vs Workday EIB, Studio, and Orchestrate](https://kiweely.com/blog/kiweely-roots-vs-workday-eib-studio-orchestrate)
-   [Orchestrate, an iPaaS, or Kiweely Roots](https://kiweely.com/blog/orchestrate-ipaas-or-kiweely-roots)
-   [Codex for Orchestration JSON: Catching the 25-Second Sync Trap Before Deploy](https://kiweely.com/blog/codex-orchestration-json-25-second-sync-trap)

## 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.
