RaaS Report Not Found Because The Report Is Not Shared With The Calling ISU
What does "400: Validation error occured. Report not found=urn" mean in Workday RaaS?
Workday says the report does not exist, but it does. The RaaS URL identifies a report by owner plus report name, so the account in the URL path has to be an account that can actually see that report. If the calling integration system user is neither the owner nor on the report's share list, Workday reports it as missing rather than as forbidden.
Quick fix
Open the report's Share tab and add the calling ISU to the shared-with list by name, then retry using the report owner's account in the URL path rather than the caller's.
Permanent fix
Decide one service account to own every integration-facing report and keep ownership there, so the owner segment of the URL never changes when staff leave or roles move. Share the report explicitly with each additional ISU that needs it. Avoid transferring report ownership to solve an access problem for one caller, because that reliably breaks every other caller whose URL still names the previous owner.
Troubleshooting
- Look at the urn in the error. The segment after urn:com.workday.report/ is the report owner the URL is pointing at, and the segment after that is the report name. Confirm both are spelled exactly as Workday has them.
- Run View Custom Report on the report and check the Owner field. If the owner is a person and your URL names an ISU, or the other way round, the URL path is wrong.
- Open the report's Share tab. You should see exactly one owner, and every other account that needs to call it listed under the shared-with users.
- If the calling ISU is missing from that list, add it explicitly. Sharing with a security group that happens to contain the ISU is not reliable here, so name the account itself.
- If two different applications each call the report with their own ISU, only one of them can be the owner. The other must appear as a shared user, and both URLs still use the owner's name in the path.
- Retry. If it still fails, run the same URL in a browser while signed in as a user you know can see the report. That separates a sharing problem from a typo in the URL.