Studio Driver Project Can't Find an External Project's Local-In After Redeploy
The error com.capeclear.mediation.MediationException: application=<CALLING_APP> - Invalid application '<REFERENCED_APP>' in local-out transport with id='InitializeI-9BIRT' and endpoint='vm://<REFERENCED_APP>/initI9PDF'. The application may not be loaded.
What does "com.capeclear.mediation.MediationException: Invalid" mean in Workday Studio?
When one Studio Project (the driver) calls another Project in the same collection over a local-in/local-out vm:// transport, Workday needs both Projects deployed together as one unit. After a Workday release or a Studio client upgrade, a collection that previously deployed and ran fine can start throwing this error because the driver Project no longer resolves the external Project's local-in endpoint.
Quick fix
Redeploy every Project in the collection together as a single deploy, not just the Project you changed.
Permanent fix
After any Workday release or Studio client version change, do a full collection redeploy and smoke-test cross-project calls before relying on the integration again, rather than assuming an unchanged Project still resolves correctly.
Troubleshooting
- Confirm every Project in the collection actually redeployed successfully, not just the driver Project, a sibling Project it depends on can silently fail or get skipped while the driver still reports a clean deploy.
- Check the local-in transport's endpoint ID on the target Project against the local-out endpoint ID the driver Project is calling, a Studio client upgrade can occasionally require re-saving a Project for its local endpoints to re-register correctly.
- Deploy the full collection as a single unit rather than redeploying just the changed Project, cross-project local transports are resolved at deploy time for the whole collection.
- If the collection was originally downloaded from a shared catalog (Customer Central or similar), verify no Project was silently excluded from the redeploy package.
Was this helpful?