OpenSite/Guides/Troubleshoot a workflow
Locate the right diagnostic surface and resolve common configuration or state errors.
- Stable identifier
opensite.help.troubleshoot-a-workflow
Prerequisites
Identify your host (desktop, OpenSiteConsole or opensite-python) and whether GUI/Python are enabled.
Steps
Start with the failure message
Record the operation, error code, input, source snapshot and complete traceback where applicable. View → Show Output opens the host journal; the interactive Console is a separate surface.
Check host and runtime
An unavailable viewport is expected headlessly. Missing opensite in system Python is not a reason to copy DLLs between unrelated installations. Keep Debug/Release runtime and toolchain contracts matched.
Check document and property state
stale_document means the handle no longer names a live session. Reopen and retain the returned handle. A stale/invalid property is not a current result. Inspect expression source, units and consent.
Check authorization
account_unavailable can be expected for protected engineering/catalog fixtures in the current production seam. Do not treat the development host as a deployment fix for product licensing.
Check the shared lane
When an editor run, debugger pause or console command owns the lane, wait or stop it before expression evaluation. A cooperative stop may wait in native code.
Expected result
You can distinguish host configuration, invalid input, closed handles, unavailable capabilities and a busy execution lane.
Limitations
This page does not provide a production website-login workaround. Keep personal credentials out of support logs.
