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
This means any done callbacks are set previously to using retry.
Thing is, when a 503 error is returned, followed by a success, the success callbacks aren't called.
The text was updated successfully, but these errors were encountered:
Hmm, I see what you mean. I need to think about how to handle this. For your specific example, I think that you can work around by using .then(successHandler, failureHandler) instead of .fail.
At this point, in my specific case, I don't have direct access to the handlers, since I do this globally, but set the handlers initially at a different point.
There might be a way to work around this, but I couldn't find a way that doesn't require changing my original AJAX call.
I have a configuration where I add a
retry
to every request globally viaajaxPrefilter
, for cases where I get timeouts from Heroku.It goes along the lines of:
This means any
done
callbacks are set previously to usingretry
.Thing is, when a 503 error is returned, followed by a success, the success callbacks aren't called.
The text was updated successfully, but these errors were encountered: