Troubleshoot VB-OS Deployment Failures
Common Issues
Section titled “Common Issues”Version Not Compiled
Section titled “Version Not Compiled”Only compiled boundary versions can be deployed.
Fix: Compile the boundary version before deploying.
Active Deployment Conflict
Section titled “Active Deployment Conflict”Only one deployment per boundary per environment can be active. Deploying a new version supersedes the existing active deployment.
Environment Not Found
Section titled “Environment Not Found”The target environment does not exist in the project.
Fix: Create the environment first, then deploy.
Boundary Version Not Approved
Section titled “Boundary Version Not Approved”If your workflow requires approval before deployment, ensure the version has been approved.
Flow Deployment Issues
Section titled “Flow Deployment Issues”Boundary Version Not Deployed
Section titled “Boundary Version Not Deployed”Flow deployment requires that the flow’s boundary version is actively deployed in the target environment.
Fix: Deploy the boundary version to the environment before deploying the flow.
Flow Not Approved
Section titled “Flow Not Approved”Only approved flow versions can be deployed.
Fix: Approve the flow version before deploying.
Next Steps
Section titled “Next Steps”- Deployments: deployment concepts
- Deploy to an Environment: deployment guide
- Manage Boundary Versions: version management
