Help
Troubleshooting
Start with the symptom and verify project, environment, time, identity, and delivery in order.
Most Teml setup problems fall into one of four paths.
No telemetry appears
Check the API key, project, endpoint, environment, time range, and SDK shutdown behavior.
Telemetry appears but not under the customer
Check the stable ID, request scope, logout reset, and trusted propagation boundary.
Customer activity is not connecting
Replay is empty or stack frames are unreadable
Check browser masking and capture, release/dist alignment, source maps, native symbols, and the recording’s related evidence.
Replay or symbols are not working
Alerts are not reaching someone
- Test the notification destination directly.
- Confirm the rule is enabled and uses the expected project and environment.
- Check the threshold, evaluation window, and sustained duration.
- Confirm the alert entered a firing state.
- Verify the on-call contact method and escalation policy when used.
Alerts or integrations are not delivering
Sign-in, API, CLI, or MCP access fails
Use the status or client error to distinguish an invalid credential, missing scope, wrong project, or client configuration problem.
Capture useful evidence
When contacting support, include:
- organization and project names, but no credentials;
- environment and exact time window with timezone;
- the dashboard URL for the affected object;
- SDK language and version;
- the complete error code or message; and
- the smallest reproduction that still fails.
Never include an API key, session token, customer secret, or unredacted sensitive payload.