# Troubleshooting Error Tracking

What to do when events do not arrive, stack traces stay minified, a connected build fails, or an old DSN key is not retired.

## No events arrive

**Cause:** The SDK sends with a DSN of a revoked key or of another project, the SDK is not
initialised before the error happens, or a limit refuses the events.

**Fix:** Open the project's **Stats** tab. Nothing at all under **Accepted** or **Refused** means
the requests never reached the project: check the DSN against the project's **Setup** tab, and the
SDK's debug output for the message "unknown or revoked DSN key" or "the DSN key does not belong to
this project". Events under **Refused** were over a rate
limit or a quota (see [Quotas](quotas.md)); events under **Dropped by the SDK** were left out by its
sampling or `beforeSend`.

## Stack traces stay minified

**Cause:** The source maps of the event's release had not been uploaded when the event arrived.
Maps are applied on arrival only; frames without one are marked **no source map**.

**Fix:** Upload the maps before you deploy the release (see
[Upload source maps](upload-source-maps.md)). For a connected app built from a Dockerfile, the
build log saying "Error Tracking: no source maps were uploaded by this build" means the build step
does not mount the `SENTRY_AUTH_TOKEN` secret (see [Connect an app](connect-an-app.md)).

## sentry-cli uploads to sentry.io

**Cause:** `SENTRY_AUTH_TOKEN` holds a token of sentry.io, or a token cut short when it was copied.

**Fix:** Use a token from the project's **Setup** tab or `dcloud errors auth-tokens create`; it
carries the Error Tracking URL. Setting `SENTRY_URL` (or `sentryUrl`) to the **Sentry URL
(sentry-cli)** the **Setup** tab shows also points the CLI here.

## A connected app's build or rollout fails

**Cause:** The Error Tracking project it is connected to was deleted, and its deletion has not
finished in the background yet. The deployment fails with "The connected Error Tracking project was
deleted; disconnect it from the app".

**Fix:** On the app's **Environment** tab, under **Error Tracking**, choose **Disconnect**, then
connect another project or deploy again.

## The previous key still accepts events after a rotation

**Cause:** The previous key is revoked only when the grace is over, every connected app that
Deutsche Cloud builds runs a build made after the rotation, and the key has received no event for 15
minutes. Apps deployed from an image or compose file are not waited for: rebuild them yourself. A rebuild that
failed, or a browser tab open since before the rebuild, holds it.

**Fix:** Rebuild the app whose rebuild failed. To end it regardless, choose
**Revoke previous key now** on the **Setup** tab (see
[Rotate the managed key](rotate-the-managed-key.md)).

## A CI job gets no upload token

**Cause:** The exchange refuses pull-request runs, jobs without `environment:`, and environments
not connected to a project; it answers `403` with the reason after "AccessDenied:".

**Fix:** Run the upload in a job with `environment:` set to the connected environment and
`permissions: id-token: write`, on a push rather than a pull request (see
[Connect a CI environment](connect-a-ci-environment.md)).

## The Transactions tab stays empty

**Cause:** `tracesSampleRate` is 0 or missing, or the SDK streams spans (`traceLifecycle:
"stream"`), which is not supported yet.

**Fix:** Set `tracesSampleRate` above 0 and leave span streaming off.

## A browser sends no profiles

**Cause:** The page is served without the response header `Document-Policy: js-profiling`, so the
browser refuses to profile.

**Fix:** Serve the page with that header.

## The API answers 503

**Cause:** The Error Tracking database is restarting. The API answers `503` "Error Tracking is
temporarily unavailable; try again shortly" with `Retry-After`. The ingest refuses every kind of
data meanwhile with `429` and a ten-second `Retry-After`; what the SDKs send during that time is not
stored.

**Fix:** Try the API again after the time `Retry-After` names. Events need no action; the ingest
takes them again once the database is back.
