RaaS Call From Studio Fails With HTTP 505 Due to Unencoded Space in Extra Path Value
What it means
A Studio integration builds the RaaS report's Extra Path from a prompt value that contains a space or other illegal URL character, for example a location name like 'Pune, India - all locations'. Workday Out transport sends that raw, unencoded value as part of the URL, and the malformed request comes back as an HTTP 505 rather than a clear validation message about the character itself.
Troubleshooting
- Log the fully-resolved Extra Path value right before the workday-out-rest call runs, not just the binding expression, since the illegal character only shows up in the resolved string.
- Check any prompt or launch parameter value feeding the Extra Path for spaces, ampersands, or other characters that are not valid in a URL.
- Confirm the failure disappears when the same call is run with a value that has no special characters, this isolates the cause to encoding rather than the report or security.
- Test the encoded version of the value directly against the report URL outside Studio to confirm it resolves before wiring the fix back into the integration.
Wrap the offending prompt value in a .replace() call in the Extra Path expression, for example replacing spaces with %20 and ampersands with %26, so the value reaching the URL is already encoded.
Build a small reusable URL-encoding expression or script include for any prompt value used in a RaaS Extra Path, and apply it consistently to every launch parameter that could contain user-entered text, not just the ones that have already caused a failure.