[Neocom II] User hitting error limit when trying to refresh data for 20 characters

[ccp-zoetrope]

We had a user come into the #esi tweetfleet slack channel saying that he hit the error limit. According to him he was trying to refresh info for 20 characters. Here is a quote:

It works fine with like 1 or 2 accounts (3-6 chars), maybe [Neocom] is not stable with many accounts/chars, OR if you frequents refresh the account/chars on the app?

Another quote that makes me think he was just refreshing a lot of characters:

Or maybe it tries to update info on 20 characters at once?

Either way, it seems like something's up when refreshing for a lot of characters :)

[Cephalostrum]

Confirming this is an issue with large numbers of characters. I have around 60-70 added into Neocom II and it appears that it is trying to poll the ESI endpoints as fast as possible. With that number of characters being refreshed at once, it's either generating malformed requests that are triggering the error, or it's just getting throttled due to the volume.
Either way, it's resolved by patience so it's definitely due to the large volume of polling requests.

[ccp-zoetrope]

ESI never throttles on volume but purely on errors, so the problem is definitely having to do with a flurry of malformed requests.