Workday errors in plain English.

Submit an Error

RaaS Call From Studio Returns 400 Report Not Found Because the Owner Segment Contains Spaces

✓ Verified RaaS (Reports as a Service) 2 lookups
The error Response :400 : Validation error occurred. Report not found=urn:com.workday.report/<ISU NAME WITH SPACES>/<INTEGRATION_NAME>null

What does "400 : Validation error occurred. Report not found=urn" mean in Workday RaaS?

Workday cannot find a report whose URN contains a space, because the space breaks the URL before the lookup ever happens. The report exists and runs normally in the UI, so the wording sends you to check the report reference when the real problem is a name.

Quick fix

Rename the owning ISU or report owner so the name contains no spaces, rebuild the report reference in the Studio assembly, and redeploy.

Permanent fix

Adopt a naming standard that bans spaces in any ISU, report owner, or report name that can appear in an integration URL, using underscores instead. Check the owner segment specifically, since it is the part of the URN people forget when they audit report names.

Troubleshooting

  1. Read the whole URN in the error, not just the report name. It has the shape urn:com.workday.report/<owner>/<report name>. Inspect every segment for a space.
  2. If the owner segment (usually the account or ISU that owns the report) contains spaces, that is the cause. A space is not parsed inside a URL and the lookup fails before Workday resolves the report.
  3. Look at the very end of the URN as well. A literal null stuck onto the report name means a Studio property or variable feeding that name resolved to nothing. That is a second, separate defect and fixing only the spaces will leave it behind.
  4. Rule out the obvious alternatives before renaming anything: confirm the report is still enabled as a web service, and confirm the calling account can run it in the UI.
  5. Deleting and recreating the report reference is a common first instinct and it does not help, because the new reference rebuilds the same URN from the same names.
  6. After any rename, rebuild the report reference in the assembly so it picks up the new URN, then redeploy.
Was this helpful?

Related errors

RaaS (Reports as a Service) RaaS Report Not Found Because The Report Is Not Shared With The Calling ISU RaaS (Reports as a Service) RaaS Call Returns Action Denied Because the Report Was Never Published as a Web Service RaaS (Reports as a Service) Studio RaaS Call Returns 404 Not Found With Multiple Report Services on One Component RaaS (Reports as a Service) RaaS SOAP Report Call Rejects Date Prompt with Invalid Format Error RaaS (Reports as a Service) RaaS Report Returns 500 Task Not Authorized While the Same Report Opens Fine in the UI RaaS (Reports as a Service) RaaS Report Call Fails with "Time Out Exceeded" on HTTP GET