How VStitcher Error Codes Are Reported
1. UI Error Dialogs
When an error occurs in VStitcher UI or Python Playground, an error dialog is displayed
The dialog includes:
A human-readable message
A VStitcher error code
These UI dialogs often provide more context than VS-CLI output.
2. Programmatic Access via BwApi
After a failed operation, the last error can be queried directly from the backend:
BwApi.GetLastError()
This returns:
The last error code generated by the VStitcher backend
Useful when:
Debugging step-by-step in Python Playground
Validating error handling logic in scripts
Investigating silent failures in headless execution
3. VS-CLI Behavior
VS-CLI may exit with:
A non-zero exit code
Limited console output
The underlying VStitcher error code is still generated internally and can often be found:
In CLI log files
By reproducing the failing operation in Python Playground and calling
BwApi.GetLastError()
Authoritative List of Error Codes
The complete and up-to-date list of VStitcher error codes is maintained on Browzwear Zendesk:
🔗 VStitcher Error Codes Reference
https://help.browzwear.com/en/articles/13066101-error-codes
This page includes:
Error code values
Meaning of each error
Recommended Debugging Workflow
Observe the error code shown in UI (if applicable)
If using Python Playground, call:
BwApi.GetLastError()
Look up the error code in the Zendesk reference
Adjust API usage, parameters, or operation order
Re-test before running scripts in VS-CLI
Key Notes
Error codes are generated by the VStitcher backend
Python Playground is the best environment to inspect errors interactively
Always rely on the Zendesk error code reference as the source of truth