Official support
The right help.
Without the guesswork.
Documentation is the first stop. When something still is not working, a focused support request gives the team the evidence needed to diagnose the actual problem.
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 only the final cascade.
3. Know your environmentInclude framework, inventory, target, and the LRSCRIPTS resource version.
4. Test conflictsTemporarily disable another resource controlling the same job, zone, UI, or event.
What to include
A useful ticket includes the product name and version, framework, dependency versions, exact error, expected behavior, actual behavior, and the shortest reproducible steps. Screenshots or short video help with visual and NUI issues.
Support boundaries
Official support covers LRSCRIPTS resources and documented integrations. Custom rewrites, unrelated third-party bugs, and undocumented edits may require separate troubleshooting.