Closed EDVLeer closed 4 years ago
Did you increase that number from 120 to something higher?
To those responding to this thread, can you give me an idea of how many assets/users you have? We have some users with schools of over 50k people and we haven't seen this issue before - however we also haven't made any changes to the API throttling, so not sure why this would just be coming up now.
Are any of you also performing API actions via automation, or do you have a very large number of admins checking things in and out? 120 really should be enough for most use-cases unless there is something scripted that's calling the API too often.
To those responding to this thread, can you give me an idea of how many assets/users you have? We have some users with schools of over 50k people and we haven't seen this issue before - however we also haven't made any changes to the API throttling, so not sure why this would just be coming up now.
Are any of you also performing API actions via automation, or do you have a very large number of admins checking things in and out? 120 really should be enough for most use-cases unless there is something scripted that's calling the API too often.
I have this issue on a fresh install, so currently around 5 assets and 3 users this issue is happening.
I get this when debug mode is on - It wouldn't be an issue for the most part except it happens within 2-3 seconds sometimes and the whole page needs to be reloaded.
Take a look at #8035 - we've done a little bit of triage there. The issue appears to be evident on the snipe-it demo too (at least it was for me).
Did you increase that number from 120 to something higher?
No, the number is still 120.
To those responding to this thread, can you give me an idea of how many assets/users you have?
Imported a few assets via CSV / users via LDAP.
Are any of you also performing API actions via automation, or do you have a very large number of admins checking things in and out?
No, it's just a fresh install.
Closing as duplicate of #8035
Please confirm you have done the following before posting your bug report:
Describe the bug API counts up after clicking in any Select2 field without any interaction. After 120 requests the results disappear with the message "the results could not be loaded" (https://snipe-it.readme.io/reference#api-throttling).
To Reproduce Steps to reproduce the behavior:
Expected behavior Show results, search for anything.
Screenshots
Server (please complete the following information):
Desktop (please complete the following information):
Error Messages
Additional context
Add any other context about the problem here.
Please do not post an issue without answering the related questions above. If you have opened a different issue and already answered these questions, answer them again, once for every ticket. It will be next to impossible for us to help you.