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
Right now, when a timeout or 500 error occurs during an API call, Sentry appears to get an error object that is actually an object with the jQuery callbacks for the API call.
We should instead (after testing it works, of course!) add a $(document).ajaxError handler to catch and report these errors properly, so we can figure out exactly which API calls are erroring or timing out, and why.
Category
ENHANCEMENT
Real-life consequences (anything community should be aware of, for instance how it affects end users)
Right now we can see that API calls are either timing out or failing, but we don't know which calls and under which circumstances these events are happening. This makes us unable to address these issues effectively.
The text was updated successfully, but these errors were encountered:
Summary
Right now, when a timeout or 500 error occurs during an API call, Sentry appears to get an error object that is actually an object with the jQuery callbacks for the API call.
We should instead (after testing it works, of course!) add a $(document).ajaxError handler to catch and report these errors properly, so we can figure out exactly which API calls are erroring or timing out, and why.
Category
ENHANCEMENT
Real-life consequences (anything community should be aware of, for instance how it affects end users)
Right now we can see that API calls are either timing out or failing, but we don't know which calls and under which circumstances these events are happening. This makes us unable to address these issues effectively.
The text was updated successfully, but these errors were encountered: