Studio Assembly Fails to Deploy: "No Bean Named vm://... Is Defined"
What it means
A Studio assembly fails at deploy time, not runtime, because a local-out step points at an internal VM endpoint (a vm:// URI used to pass messages between steps) that has no matching local-in step defining that exact endpoint name anywhere in the assembly. Studio validates this internal wiring when it builds the assembly, so a typo or a missing local-in step surfaces immediately as a deploy failure.
Troubleshooting
- Open the assembly and list every local-in and local-out step along with the endpoint string each one uses.
- Compare the endpoint named in the deploy error character-for-character against every local-in endpoint in the assembly, since these are simple string matches with no fuzzy resolution.
- Check whether the matching local-in step lives in a different swimlane, or was disabled or deleted during a recent edit, since either case will produce this same error.
- Redeploy after fixing the mismatch. Because this is a build-time validation, a successful deploy confirms the wiring is now consistent.
Correct the local-out endpoint string (or add the missing local-in step) so it exactly matches an existing local-in endpoint in the assembly, then redeploy.
Adopt a naming convention for internal vm:// endpoints and keep local-in/local-out pairs visually close together in the assembly layout during development, so a rename on one side is far less likely to be missed on the other.