Improve the error given when purging cache fails by our plugin.
available
Pieter Daalder
When something goes wrong purging the cache, the error given is "vague" at best. If possible it should contain the API request payload and response.
Log In
Thomas Audunhus | Acting CEO | Servebolt
available
Servbolt Optimizer 3.5.40 has been released with improvements with regards to the error message being displayed when an error occurs related to purging.
Thomas Audunhus | Acting CEO | Servebolt
planned
Thomas Audunhus | Acting CEO | Servebolt
under review
Pieter Daalder
Sure!
- If Cloudflare is throttling us, doing a purge will fail with this error. This results in the client checking the options we mention, finding nothing wrong, and trying again. Increasing the load/amount of purges being done and as a result not helping with the situation.
- Having the payload sent for the request, and the response would already help greatly. This might however be an information overload for most users. If there are distinct differences between the status codes returned for various things that can go wrong it might be good enough to only give that status code, paired with the action our plugin tried to perform. (Full purge, single URL purge) If that doesn't allow the user to make the distinction between various scenarios, the full payload/response might be better.
- Although I have been seeing these kind of errors more often recently, I haven't been able to spot distinct patterns to see/make improvements on that end. So no, I don't see specific scenarios where the cache purge fails more frequently.
Thomas Audunhus | Acting CEO | Servebolt
Hey Pieter Daalder, thanks for your feedback! I have a few more questions for you:
- Can you provide an example of a situation where the error message was not helpful?
- What specific information would you find helpful in the error message?
- Are there any specific scenarios where the cache purge fails more frequently?