OpenSite/Support
Prepare a report that another person can reproduce.
Start with the right help
OpenSite/FAQ · OpenSite/Guides/Troubleshoot startup · OpenSite/Guides/Troubleshoot a workflow · OpenSite/Known limitations. For a failed edit, record the field/value/unit and exact message. For a run, record the script and traceback.
Report checklist
- OpenSite build/commit or distributor package name, Windows version and architecture.
- Whether this is Desktop, Console, Python workbench, headless host or CLI.
- Extension/runtime versions relevant to the problem.
- Smallest steps that reproduce it, starting from a new practice file when possible.
- Expected result and actual result, including units.
- Exact error text and the relevant Output/traceback excerpt.
- A minimal non-confidential file/script and a genuine screenshot where helpful.
Copyable report outline
OpenSite build/package: Operating system / architecture: Surface and extension: Steps to reproduce: 1. 2. Expected result (include units): Actual result: Exact error / relevant Output: Minimal sample attached: Does it reproduce with a new practice document?:
Protect project information
Do not send passwords, tokens, complete proprietary models or personal data unnecessarily. Use a reduced practice example. Keep the original file when reporting a possible preservation/recovery defect.
Where to send it
Use the support channel supplied with your authorized build or your established BathAfrica product contact. Developers with repository access can use the project’s issue process. No public support email, ticket endpoint or response-time commitment is established by the reviewed source.
