# SENTRY_INSTALLATION_CONFLICT

- Surface: API
- HTTP status: 409
- Recommended action: `REVOKE_ACTIVE_INSTALLATION`
- Details: `{ activeInstallationId: string, recommendedAction: "REVOKE_ACTIVE_INSTALLATION" }`

## Remediation

Revoke the installation named in details.activeInstallationId before installing a new one

## Cause

The Environment already publishes its Flag changes to a Sentry organization. Sentry's change-tracking payload carries no environment, so a second installation would interleave two Environments' toggles into one audit log.

## Fix

Revoke the active installation named in `details.activeInstallationId`, then install the new one. Sending the same `installationId` again is a replay and returns the existing installation instead.

## Related

- [SENTRY_INSTALLATION_NOT_FOUND](https://splitch.dev/docs/error/SENTRY_INSTALLATION_NOT_FOUND)
- [IDEMPOTENCY_KEY_CONFLICT](https://splitch.dev/docs/error/IDEMPOTENCY_KEY_CONFLICT)

Source: https://splitch.dev/docs/error/SENTRY_INSTALLATION_CONFLICT