OpenSite/Guides/Inspect Output
Use the right diagnostic surface for the operation you ran.
- Stable identifier
opensite.help.inspect-output
Prerequisites
A desktop session. Reproduce a small non-confidential problem if possible.
Steps
Open the shared journal
Choose View → Show Output. It reports host/application messages; workbench scripts use source python.script. The interactive Console transcript is separate.
Find the relevant event
Match the source and time/order to the operation. Use available filtering/details rather than assuming every older message belongs to the latest run.
Read the useful details
Keep the operation, error category and actionable message. For Python, record the file/line and final exception. For startup/viewport failures, keep the reported status and build.
Reproduce once with a small case
Save your work, reduce the input, run the intended action and note what changed. Avoid launching repeated runs while the lane is busy.
Prepare a report
Use OpenSite/Support. Remove credentials, account tokens, personal paths and confidential project information before sharing diagnostic text or screenshots.
Expected result
You can associate a useful diagnostic with one reproducible action.
Limitations
An output “success” message is not independent verification of an engineering calculation.
