# Troubleshooting

> Start with the symptom and verify project, environment, time, identity, and delivery in order.

Canonical page: https://anectico.com/docs/help/troubleshooting/


Most Anectico setup problems fall into one of four paths.

## No telemetry appears

Check the API key, project, endpoint, environment, time range, and SDK shutdown behavior.

[No data is appearing](/docs/help/no-data)

## Telemetry appears but not under the customer

Check the stable ID, request scope, logout reset, and trusted propagation boundary.

[Customer activity is not connecting](/docs/help/identity-not-linking)

## 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](/docs/help/replay-and-symbols)

## Alerts are not reaching someone

1. Test the notification destination directly.
2. Confirm the rule is enabled and uses the expected project and environment.
3. Check the threshold, evaluation window, and sustained duration.
4. Confirm the alert entered a firing state.
5. Verify the on-call contact method and escalation policy when used.

[Alerts or integrations are not delivering](/docs/help/alerts-and-connections)

## 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.

- [Authentication or access is failing](/docs/help/authentication-and-access)
- [MCP or CLI is not working](/docs/help/agents-and-cli)

## 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.

If the issue persists, follow [Contact support](/docs/help/support) to share that evidence safely.
A registry 404 during early access does not mean the SDK is unsupported: use the artifact or
repository access supplied during onboarding, as described in
[Choose an integration](/docs/start/choose-integration#install-during-early-access).