Unhandled errors
Capture runtime JavaScript failures that users may hit in production browsers.
LA Sentry browser
LoopAware's browser LA Sentry harness captures unhandled errors and rejections through an origin-bound public endpoint so frontend failures can be reviewed beside site feedback and traffic.
A browser script cannot safely hold a protected server-side token. LoopAware uses a dedicated browser ingest path that validates the configured site ID and allowed origin instead.
<script src="https://loopaware.mprlab.com/la-sentry.js" data-site-id="..."></script>Capture runtime JavaScript failures that users may hit in production browsers.
Record failed async paths that otherwise disappear into console noise.
Use the browser harness for explicit `LASentry.captureError` calls when code has known failure boundaries.
Use browser capture for public frontend errors that need to be triaged by the same team reviewing site signals.
Capture browser JavaScript errors in LoopAware LA Sentry with allowed-origin protection instead of exposing a server-side ingest token. It is useful when developer errors should be reviewed beside site feedback and traffic instead of in a separate monitoring view.
Confirm the workflow is tied to the correct LoopAware site, then check the first dashboard records with the people who will act on them.