Studio RaaS Call Returns 404 Not Found With Multiple Report Services on One Component
The error com.capeclear.capeconnect.transport.BadRequestException: error from returned HTTP status: 404 Not Found URL=https://wd5-impl-services1.workday.com/ccx/service/
What it means
A Studio integration calling two different RaaS reports through separate report retrieval services layered onto the same workday-out-rest component only resolves one of them at a time. The other report call 404s because the component's endpoint path can only match a single report reference per deployment.
Troubleshooting
- Confirm the 404 happens on one specific report call while a different report call from the same integration succeeds, this points to a component configuration conflict rather than a bad report definition.
- Open the workday-out-rest component and check how many separate report retrieval services feed into it, more than one attached to a single start component is the signal.
- Compare the Extra Path expressions (intsys.reportService.getExtrapath(...)) for each report service, if they resolve against the same component instance, only the first-bound path resolves correctly at runtime.
- Test with each report service deployed against its own workday-out-rest component to confirm the conflict is the component sharing, not the report or its security.
⚡ Quick fix
Remove the extra report retrieval services from the shared workday-out-rest component and re-add each report to the component individually so Studio generates one report service per report reference automatically.
✓ Permanent fix
When an integration needs to call multiple RaaS reports, give each report its own report retrieval service and workday-out-rest component pairing rather than layering several reports onto one shared component.
Was this helpful?