chore: temporarily disable Sentry denyUrls to debug "Load failed" errors #15958
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
- Comment out denyUrls configuration in Sentry client setup - This allows third-party service errors (on artsy.net domain) to reach Sentry - Previously blocked: braze.com, doubleclick.net, googletagservices.com related errors - Will help identify which external services cause "TypeError: Load failed" - Temporary change for debugging - will re-enable after analysis 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
Merged
This was referenced Aug 6, 2025
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.
Problem
We're seeing frequent "TypeError: Load failed" errors in Sentry but lack visibility into which third-party services might be causing them. Our current Sentry configuration blocks errors related to external services (Braze, Google Tag Manager, DoubleClick, etc.) via the
denyUrlsfilter.Solution
Temporarily disable the
denyUrlsconfiguration in Sentry client setup to allow third-party service errors (occurring on our domain) to reach Sentry.I will monitor Sentry for 24 hours to collect data and then revert this change.
What this reveals
Impact
cc: @artsy/diamond-devs