---
title: "Why does Workday RaaS time out for non-admin users but…"
description: "RaaS applies the issuing user’s security and a 5-minute api.workday.com limit. Constrained users hit slower filters—shrink the report or raise wait time."
url: https://kiweely.com/guides/workday-raas-timeout-non-admin-user
---

# Why does Workday RaaS time out for non-admin users but work for admins?

RaaS applies the issuing user’s security and a 5-minute api.workday.com timeout. Constrained users can exceed that limit on the same report—narrow filters or prove the gap in the tenant UI.

-   **Checked** against Workday on November 17
-   Applies to **Workday Reports as a Service (RaaS)**
-   2 min read
-   Published November 17
-   By Kiweely

RaaS that finishes for an administrator and times out for everyone else is usually **the same report under different security**, not a broken URL. Workday applies the issuing user’s object and data-level security. Constrained users can trigger heavier filtering and miss the gateway deadline even when they receive fewer rows.

## Timeouts Workday publishes

From Workday’s WQL and RaaS comparison:

| Path | RaaS timeout |
| --- | --- |
| SOAP or REST from a tenanted host | Up to 6 hours |
| API calls through **api.workday.com** (WCP Gateway) |  **5 minutes** |

Extend apps and many orchestrations call RaaS through the gateway path. A read timed out / socket timeout on that path often means the report did not finish inside five minutes for that user.

Advanced report options require a valid tenant account and permission to view the report and its data for external report links. That same security model applies when the report runs as a service.

## Prove the bottleneck is the report

1.  Run the custom report in the tenant as the admin (or unconstrained) account. Note duration.
2.  Run the same report as the non-admin user with the same prompts. Note duration.
3.  Call the RaaS URL as each identity (or through the app’s ISU vs an admin test). Compare times to the 5-minute gateway limit.
4.  If the UI report is already slow for the constrained user, raising an app HTTP timeout cannot beat the gateway cap on api.workday.com.

## Fix the report for constrained users

| Change | Why it helps |
| --- | --- |
| Narrow prompts and filters | Less security evaluation and less data |
| Prefer indexed data sources | Workday reporting guidance favors indexed sources for performance |
| Avoid wide cross-worker custom-object designs when a model-backed source exists | Custom-object-heavy reports are common sources of slow constrained runs |
| Share the report and required domains with the issuing user or ISU | Missing access can cause retries and failures that look like hangs |
| For Orchestrate, adjust connect timeout and retries only after the report itself is acceptable | Education material allows extended connect timeout for long reports; it does not remove the gateway limit |

Background and web-service report processing also carries Workday’s broader reporting time limits (including multi-hour caps for some background paths). Treat those as outer bounds; gateway callers still have five minutes.

Kiweely Vine can help you compare RaaS versus WQL options and inspect report security with consent. It cannot raise Workday’s api.workday.com timeout.

## Frequently asked questions

### What is the RaaS timeout on api.workday.com?

Workday documents a 5-minute timeout for RaaS API calls through the WCP Gateway (api.workday.com). Tenant-hosted RaaS SOAP and REST allow up to 6 hours.

### Does RaaS return the same rows for every user?

No. RaaS honors object and data-level security for the issuing user. Constrained users can see fewer rows and still take longer because of security evaluation.

### Is raising the HTTP client timeout enough?

Only as a stopgap when you call through a client you control, and never past Workday’s gateway limit on api.workday.com. Fix the report cost for constrained users.

## Sources checked

-   [Reference: WQL and RaaS Comparisons](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/workday-query-language-wql-/jvv1659563380308.html)
-   [Set Up Advanced Options for Custom Reports](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/set-up-reports/blz1474396724926.html)
-   [Reference: Reporting Limits](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/report-performance-and-limitations/dan1370796644559.html)
-   [Orchestration Data Access](https://doc.workday.com/workday-education/en-us/course-manuals/creating-integrations-using-workday-orchestrate/orchestration-data-access.html)

## Related guides

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

-   [### Custom reports and RaaS when an AI assistant is helping you build them Advanced and search reports can be enabled as web services. Copy a standard report before you expose it, keep the namespace stable, and use Deployment Agent only to find which custom reports exist in the tenant. You still choose the output type and the security.](https://kiweely.com/guides/ai-workday-custom-reports-raas-for-consultants)
-   [### 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)
-   [### How to Set Up Workday RaaS: Turn a Custom Report into a Web Service, Step by Step To set up Workday Reports as a Service, make an advanced or search report, select Enable As Web Service, then copy the URL from Web Services > View URLs. Prompts, formats, security and common failures.](https://kiweely.com/guides/workday-raas-setup)
-   [### Should I use RaaS, WQL or the REST API to extract data from Workday? Use RaaS for a saved report’s output, WQL for a filtered, grouped or paged extract of up to 1 million rows, and REST for small, low-latency reads of one resource. Limits and sources are in the table.](https://kiweely.com/guides/workday-raas-wql-rest)

### More guides on Integrations and APIs

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

-   [Why does a custom object update return 403 with escaped HTML in the body?](https://kiweely.com/guides/workday-custom-object-patch-403-escaped-html)
-   [Why does Create WCP API Client return 409 for an ISU?](https://kiweely.com/guides/workday-create-api-client-409-isu-already-has-client)
-   [How do I set an Integration System Security Group for an Integration System User?](https://kiweely.com/guides/workday-issg-for-integration-system-users)
-   [SOAP vs RaaS Basic Auth vs OAuth: which Workday credentials do I use?](https://kiweely.com/guides/workday-soap-vs-raas-vs-oauth-authentication)
-   [Which Object Transporter migration paths does Workday support?](https://kiweely.com/guides/workday-object-transporter-migration-paths)
-   [Sandbox to Production Object Transporter checklist](https://kiweely.com/guides/workday-object-transporter-sandbox-to-prod-checklist)
-   [Object Transporter or Configuration Change Tracker: which moves Workday config?](https://kiweely.com/guides/workday-object-transporter-vs-configuration-change-tracker)
-   [Why does Object Transporter block single-instance migration from Production?](https://kiweely.com/guides/workday-ox-production-single-instance-limits)

### From the blog on Integrations and APIs

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

-   [Same Report, Different Rows: Why a Workday Custom Report Changes Output When Enabled as RaaS](https://kiweely.com/blog/why-workday-reports-differ-between-run-and-raas)
-   [What Happens When a 50,000-Row Workday EIB Times Out Halfway Through (and How to Batch It Safely)](https://kiweely.com/blog/splitting-large-workday-inbound-eib-loads-safely)
-   [Mass Action Tables Are Quietly Replacing Routine HR EIBs, Except Where Dirty Source Data Lives](https://kiweely.com/blog/when-mass-action-tables-replace-workday-eibs)

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