Guide

Troubleshooting & support

Fix common problems and send a useful report to support.

Quick steps

Note the page link, action and exact visible error. Save any unsaved wording or report configuration before reloading.
Check your connection, signed-in account, filters and any access or limit notice; retry once where offered.
If the issue persists, email hello@stream-markets.com with those details and the approximate time.

For an incorrect number, description, ownership, coordinate or source on an existing record, use Report error in its header or the row flag. Data & accuracy explains the correction form and withdrawal.
For broken controls, crashes, missing records, feature requests, payment questions or a form you cannot use, email hello@stream-markets.com. Include the affected page and what you expected to happen.
StreamBot can help prepare a concise description, but it cannot create a support ticket, submit a correction or email someone for you. A chat response is not a support receipt.

Check the network connection, reload once after preserving unsaved work, and sign back in if the session expired. A sign-in prompt, paid-data gate, empty result and server failure need different remedies.
For an empty table, clear search and filters. For a broken deep link, try finding the record through its browse table and note both URLs.
For a failed follow, save or correction, check the confirmation or receipt. If a control reverts, do not assume the change persisted. Avoid repeated submissions while one is still running.
If a phone control is hidden, close the keyboard or minimise StreamBot and use the page’s horizontal scrolling or row detail control. If it remains inaccessible, include the device/browser and control name in your report.
Do not clear browser storage as the first troubleshooting step: it can remove local drafts, preferences or access to anonymous chat history.

Include the page URL, company/project or report name, steps to reproduce, expected result, actual result, exact visible message and approximate time with time zone.
For display or keyboard problems, include browser, device, screen size or zoom and an optional screenshot with private information removed.
For a data issue, add the field, displayed value, suggested correction and public source/date if known. For billing, include account email and charge date; for API, include only a redacted request.
Never send passwords, full payment-card details, API keys, session cookies or sign-in links. There is no guaranteed response or correction completion time.