Workday Out Returns 404 notfound When an Assembly Defines Two Report Services
What does "Integration Failed. com.capeclear.mediation.MediationException: Workday Out transport id=Emp_RAAS_Call" mean in Workday Studio?
A Workday Out call to a report comes back 404 even though the report exists and a different report in the same assembly works fine. When an assembly defines more than one report service, only one of them ends up wired to the endpoint the call resolves to, so calls aimed at any other service land on a URL that does not exist.
Quick fix
Point every report call in the assembly at a single report service that lists all the reports it needs, then redeploy and rerun.
Permanent fix
Define one report service per assembly and add each report to it as an entry, rather than creating a separate service per report. Adding reports through the outbound component generates and references that single shared service consistently, which removes the ambiguity altogether.
Troubleshooting
- Call the report URL directly outside the assembly using the same credentials. A 404 there is a report or security problem, so stop and fix that first.
- Count the report services defined in the assembly. Two or more separate services is the shape that causes this, and one service with two reports is not.
- Check which report service the failing step references, and whether that service is the one actually attached at the start component.
- Note which report succeeds. The one that works is normally the service the endpoint resolved to, and every other service returns the 404.
- Be aware that deleting the working report service can make the failing one start working. That confirms only one service is ever in play, it does not mean the deleted service was faulty.