-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
fix(preprod): handle integration permission errors #102981
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
+260
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
rbro112
approved these changes
Nov 10, 2025
Issues attributed to commits in this pull requestThis pull request was merged and Sentry observed the following issues: |
Jesse-Box
pushed a commit
that referenced
this pull request
Nov 12, 2025
This is a common issue for orgs when they first integrate and we want extra visibility around when it happens. I see other parts of our integrations codebase treats this as a `IntegrationConfigurationError`, so doing the same here. I also noticed that these were being retried up to our limit which doesn't make sense since it is not a recoverable error. I added `IntegrationConfigurationError` to our error ignore list. Resolves EME-611
andrewshie-sentry
pushed a commit
that referenced
this pull request
Nov 13, 2025
This is a common issue for orgs when they first integrate and we want extra visibility around when it happens. I see other parts of our integrations codebase treats this as a `IntegrationConfigurationError`, so doing the same here. I also noticed that these were being retried up to our limit which doesn't make sense since it is not a recoverable error. I added `IntegrationConfigurationError` to our error ignore list. Resolves EME-611
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a common issue for orgs when they first integrate and we want extra visibility around when it happens. I see other parts of our integrations codebase treats this as a
IntegrationConfigurationError, so doing the same here.I also noticed that these were being retried up to our limit which doesn't make sense since it is not a recoverable error. I added
IntegrationConfigurationErrorto our error ignore list.Resolves EME-611