Orchestration End Component: Response Body Validation Warning Won't Clear
What does "Flow contains a resource that is not used" mean in Workday Orchestrate?
When you configure an Orchestration End component's response body with the Create Structure option and later switch it to Reference Existing Data, Workday leaves behind a phantom validation warning pointing at a resource ID that no longer exists anywhere in the flow. Workday's product team confirmed this is a known bug, and it does not block your build.
Quick fix
Confirm the orchestration still builds and compiles despite the warning, then proceed with deployment. Do not spend time trying to make the phantom warning disappear by re-editing the response body repeatedly, doing so just generates additional copies of the same warning.
Permanent fix
There is no customer-side fix. Workday's product team has an internal ticket open for the leftover-reference bug in the Orchestration End component's validation logic. Watch your release notes for a fix, or reference this behavior in a support case if you want your tenant linked to the existing ticket.
Troubleshooting
- Reproduce the pattern: on a synchronous orchestration's End component, configure the response body via Create Structure, save, then reconfigure the same field via Reference Existing Data and save again.
- Check whether the warning references a resource ID (a UUID-style string) that no longer appears anywhere in your orchestration's structure. That pattern matches this specific known bug rather than a genuine unused-resource warning.
- Confirm the orchestration still builds and compiles successfully despite the warning. That is what distinguishes this cosmetic bug from a real blocking validation error.
- If the warning references a resource ID you can still find elsewhere in the flow, that is a different, real unused-resource warning and should be investigated on its own rather than assumed to be this bug.