Studio Splitter Fails with "No Split Message Was Generated" Converting JSON to XML
What it means
When a Studio integration uses the delivered json-to-xml converter followed by an xml-stream-splitter to loop through the converted message, the splitter can throw this MediationException if the resulting XML doesn't actually contain repeating elements at the path the splitter is configured to split on. Workday treats a zero-match split as a failure rather than an empty result.
Troubleshooting
- Log the XML output of the json-to-xml converter step right before it reaches the splitter, don't assume the conversion produced the structure you expect.
- Check the splitter's configured XPath against that logged XML: a JSON array that collapses to a single object during conversion won't match a splitter path expecting multiple sibling elements.
- Confirm whether the splitter's "No Split Message Error" property is set to true (the default) or false; leaving it true is what turns a zero-match case into a hard failure instead of an empty pass-through.
- Test with a payload known to produce at least one matching element to confirm the splitter path itself is correct, isolating a path problem from a data problem.
Set the splitter's "No Split Message Error" property to false so a zero-match input doesn't abort the integration, if that outcome is acceptable for the use case.
Validate the JSON payload shape upstream (or add a conditional check) so the splitter only ever receives XML guaranteed to have the expected repeating structure, rather than relying on the error flag as a workaround for genuinely empty input.