Troubleshooting

No Lightstreamer activity appears

1. Confirm that the page uses the official Lightstreamer Web Client.
2. Open Workbench in Chrome or Firefox developer tools.
3. Check Capture and Coverage.
4. Select Page Scope.
5. Clear the active Filter.
6. Reload the page.

If Coverage is limited, follow the displayed recovery action. Missing Evidence does not prove that an event did not occur.

Extension context invalidated

This can occur after an extension update or reload. The open page can still contain the previous content script.

1. Reopen DevTools.
2. Reload the inspected page to attach a fresh bridge.

For an unpacked build, keep Developer mode enabled in chrome://extensions.

Firefox temporary developer installs use about:debugging#/runtime/this-firefox and disappear when Firefox exits. Regular users should use the signed Mozilla Add-ons release once available.

Older Evidence is missing

History has rolling limits. At capacity, Workbench removes the oldest Evidence while Capture continues. Export the records you need before they expire.

Check the retained range and Evidence Gaps before drawing conclusions. See retained history.

History uses memory

IndexedDB can be unavailable at startup or fail during capture. Workbench uses the smaller memory capacity for the rest of that Panel Session.

Check Notifications for the cause. Restore IndexedDB before opening a new panel. The new panel starts empty. Memory storage does not reduce Coverage by itself.

Local Injection is unavailable

1. Select a live target Subscription.
2. Select compatible Item Update Evidence.
3. Close a protected Draft or Scenario that owns a different target.

Retired objects remain available for inspection but cannot receive Local Injection.

An MCP agent cannot find a panel

Use the connection checks. Confirm that the agent app starts the MCP server and the intended Workbench panel is open.

If Agent access and setup is missing, install a matching packaged extension. If you loaded that download unpacked, use its Chrome-assigned ID in the npm setup command.

For Firefox, use companion 0.1.8 or later with the approved add-on ID. The same companion handles Chrome and Firefox panels; select the exact panelSessionId when several are open. A nonstandard Firefox profile registry location may need LSEW_FIREFOX_PROFILES_DIR in the MCP environment. See MCP setup.

The interface differs from this guide

Check the installed version in chrome://extensions or Firefox about:addons. Compare it with Release notes.

If the problem continues, contact Support. Remove private data before sharing a report.