Troubleshooting Integrations

Sentry integrates with many third party services to make your development experience easier. Unfortunately, we can’t always automatically update some of these services when critical data within Sentry is changed. This document is meant to help you navigate any expected behaviour resulting from these settings being changed. In some cases, we may need your team to manually intervene to get the integration working smoothly again.

If you've changed your organization slug

• Any integration that creates links directly to Sentry issues will continue creating correct links going forward, but existing links will no longer work as expected. This includes, for example, Slack notifications containing links to Sentry alerts, and Jira tickets that link to Sentry issues.

• Most deployment integrations use Sentry CLI under the hood, which requires providing your organization slug by way of the SENTRY_ORG environment variable. For these integrations to continue working, you must manually update this variable on the appropriate service.

• If you're using any of the following integrations, you need to manually update the organization slug to maintain functionality:

  • Bitbucket Pipelines
  • GitHub Actions
  • Netlify
  • Vercel
  • Grafana
  • Split
  • Segment
  • FullStory
  • OpenReplay
  • SourceGraph