You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm getting a number of 504 errors from https://res.cloudinary.com that I want to suppress. I am trying to suppress the error results from this domain when I add the Sentry interceptor. E.g.
failedRequestTargets can either be a plain string or an regex. But there's no need to define regex groups aka (). So in your case this should work fine:
My bad, I misunderstood your question. The regex supplied in failedRequestTargets needs to match a full URL, including the scheme and potential url parameters. Something like this should work:
@courville Apologies for the confusion - 7.1.0 fixed an issue where before that versoin, errors wouldn't be reported even though we communicated that they would. In general we don't change behavior like this outside of major version bumps.
Activity
markushi commentedon Mar 6, 2024
Hi @barry-irvine, thanks for reaching out!
failedRequestTargetscan either be a plain string or an regex. But there's no need to define regex groups aka(). So in your case this should work fine:My bad, I misunderstood your question. The regex supplied in failedRequestTargets needs to match a full URL, including the scheme and potential url parameters. Something like this should work:
15 remaining items
romtsn commentedon Mar 27, 2024
@barry-irvine did you manage to verify whether the updated answer works for your case?
courville commentedon Mar 27, 2024
thanks for the feedback and nova-video-player/aos-Video@930b65b did the trick.
This was quite a change of behavior and unexpected.
Sorry for the noise.
kahest commentedon Mar 28, 2024
@courville Apologies for the confusion - 7.1.0 fixed an issue where before that versoin, errors wouldn't be reported even though we communicated that they would. In general we don't change behavior like this outside of major version bumps.
markushi commentedon Apr 3, 2024
Closing this for now, if you think there's still an issue simply re-open this ticket.
barry-irvine commentedon Apr 15, 2024
@markushi I've finally got the updated code in production and can still see the 504 cloudinary errors in Sentry.
This was the final implementation. Did I do something wrong?
And yet I see a 504 error for "https://res.cloudinary.com/dtljonz0f/image/upload/c_fill,g_auto,h_333,w_250/gc-v1/las-vegas/Favorite-Bistro7206_0.jpg" in the console. It looks like we get the 504s when the user's device is offline and Coil (the library we use for image processing) doesn't even bother to send the image request to Cloudinary because it knows they're offline so it just returns a 504 straightaway.
angusholder commentedon Apr 23, 2026
For anyone who was having this issue of non-existent 504s being reported to Sentry, it was just fixed in 8.40.0 here: #5299