RaaS Report Call Fails with "Time Out Exceeded" on HTTP GET
What it means
An external system calling a RaaS report as a web service ran long enough to hit one of two Workday-side limits: either the calling account's session timeout closed the connection mid-pull, or the report itself exceeded Workday's background processing time allotment for reports and web services.
Troubleshooting
- Confirm which limit was actually hit: check whether the calling account, especially an ISU pulling a large volume of data, has a short session timeout configured, versus the report genuinely taking longer than Workday's processing allotment to generate.
- If the failure is tied to a specific day or time, for example only Monday runs right after a heavier weekend batch, check for external load or a backlog on the calling system around that window rather than assuming Workday itself is slow.
- Test the same report call against a smaller date range or filtered dataset to see whether runtime scales with data volume, confirming a data-size cause rather than a network or auth issue.
- Review the calling ISU's or integration system user's session timeout setting versus how long the report call typically takes to complete.
Re-run the call outside the affected window, or against a narrower report scope, to confirm it's a volume or timing issue rather than a permanent break.
Extend the Session Timeout Minutes on the calling account via the Edit Workday Account task (Workday defaults to 20 minutes for most accounts) so long-running report pulls have room to complete, and if the report itself is simply large, split it into smaller scheduled pulls instead of one large synchronous call.