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.

LRS Notifications product artwork — Official LRSCRIPTS support pathDocs / diagnostics / resolution

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 the LRSCRIPTS resource version and any framework or integration involved.

4. Test conflictsTemporarily disable another resource controlling the same UI, notification path, job, zone, or event when appropriate.

LRS Notifications support

For LRS Notifications, include version 1.1.0, the export or event being called, whether framework routing or a compatibility listener is enabled, the expected alert, the actual result, and the first relevant F8/server-console error. If duplicate notifications appear, identify any other notification resource or framework listener that is still active.

Notifications documentation

What to include

A useful support request includes the product name and version, framework where relevant, 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.