OFFICIAL SUPPORT
Get The Right Help.
Without The Guesswork.
Documentation is the first stop. When something still is not working, the support process is designed to collect the information needed to diagnose the actual problem instead of sending customers in circles.
Before opening a support request
1. Check the docsConfirm installation order, dependencies, configuration and known release notes.
2. Capture the first errorCopy the first relevant server-console or F8 error, not just the final cascade.
3. Know your environmentInclude framework, inventory, target and the LRSCRIPTS resource version.
4. Test conflictsIf another script controls the same job, zone, UI or event, test with the conflict disabled.
What to include
A useful ticket should include the product name, version, framework, dependency versions, exact error text, what you expected to happen, what actually happened and the shortest steps that reproduce it. Screenshots or a short video are helpful for visual/NUI problems.
Support boundaries
Official support covers LRSCRIPTS resources and their documented integrations. Custom server rewrites, unrelated third-party script bugs and undocumented edits may require separate troubleshooting. The goal is to keep support clear about what is actually failing.