I want to know what happens when I disable a project’s DSN / Client Key - whether that pauses the project, stops events and quota use, what the app sees in the network console, and how long the change takes to apply.

Disabling a Client Key (DSN) under Project Settings → Client Keys (DSN) stops Sentry from accepting events sent with that key. Those events are dropped and do not consume quota.

This only disables that specific key. If the project has other active Client Keys, events sent with those keys will continue to be ingested. To pause all ingestion for the project, disable every active key (or stop sending events from the SDK).

If the SDK is still running with the disabled DSN, the app will keep trying to send events. Sentry rejects those requests with HTTP 403 and a body like event submission rejected with_reason: ProjectId. This does not affect the app’s functionality; it only results in failed ingest traffic, which is often visible in the browser console.

Config refresh is not always immediate, so expect a short delay before the disable fully takes effect across ingest.

To avoid failed requests entirely, disable or skip SDK initialization in your code instead of only turning off the key. See How do I disable Sentry in specific environments?.

For more information about what a DSN is and how to rotate keys, see the DSN documentation.