RaaS Extra Path Call Fails with 505 When a Business Site Prompt Value Contains a Comma
The error Integration Failed. com.capeclear.mediation.MediationException: Workday Out transport id=Find_Country_ISO_Code encountered problem sending to endpoint '...'. Details: BadRequestException : Error code : unknown Response : com.capeclear.capeconnect.transport.BadRequestException: error from returned HTTP status: 505 Root Cause: BadRequestException : Error code : unknown
What it means
A Studio integration builds the RaaS extra path with getExtrapath and passes a Business Site prompt value straight into the URL. When that value contains a comma, such as a location name like "Pune, India, all locations", the unescaped comma breaks the URL and Workday returns a transport level 505 instead of report data.
Troubleshooting
- Print or log the fully assembled extra path string before the call executes, look for unescaped commas, spaces, or other punctuation from the prompt value.
- Confirm which prompt is a free text or reference value that can legitimately contain a comma, business site and location names are common offenders.
- Test the exact same report and prompt combination manually in the browser to confirm the 505 is tied to the value's punctuation and not the report definition itself.
- Check whether the value came from a getExtrapath call chained directly from another attribute versus a hardcoded, already-encoded string.
⚡ Quick fix
URL-encode the prompt value before appending it to the extra path, or wrap it in Studio's encode function so commas and spaces are escaped.
✓ Permanent fix
Build extra path construction in Studio through a single reusable encoding step for every prompt value, rather than concatenating raw attribute values directly into the URL, so any future prompt with punctuation in its value doesn't need a one-off fix.
Was this helpful?