If it
ever works, it’s not an API issue or an issue with the addon needing to be rebuilt, it’s a connectivity issue with the server. Maybe it’s a concurrency issue with the server (the Settings page is unique compared to other pages for the following reasons):
- 13 underlying API request are run in parallel to get all the info needed to build that page.
- Normally API requests will retry once if they fail for any reason), but there is no automatic retry mechanism here because they are all running in parallel.
My guess is your server is getting connectivity errors once in awhile, but that page having 13 requests and then
not doing a retry on those gives you an exponentially higher probability of any single one intermittently failing and causing the page to not work.
For example, say your server was failing 10% of the time on the API requests, normally that would cause an overall 1% failure rate because the 10% of the time it failed, it would try again and fail 10% of that time 10% of 10% = 1%.
Take the same failure rate of 10% and multiply that by 13 (concurrent requests), and throw in no retry mechanism when one does fail, and you are looking at a 75% chance that at least one request will fail and cause the Settings page to not work.
TL;DR: if your server has a “minor” connectivity issue, it will be a lot more noticeable on the Settings page because of how that page works.