I've been building my app for the last week and just implemented Appwrite cloud (couple of days). For some reason the rate limit triggered even though all my graphs in the project show no information (which is strange).
I've not been requesting that much in all honesty. A query per minute or 2. When debugging more than that but that's for a short few minutes of debugging. Am I missing something?
Summary
User is experiencing a rate limit issue while debugging their app. They are confused as to why the rate limit is triggering even though they have not been making many requests. They mention that logging in and out might be the problem. They also ask if this could be a bug. In the end, the issue is marked as solved and it is mentioned that read requests are not subject to rate limits. Solution: The user is advised to check a related issue on GitHub for more information on configuring rate limits.
@Steven Hi Steven, I thought this was solved but you said that read requests are not subject to rate limits. However I login and request a list (which is empty now) and I still hit the rate limit. Could this be a bug?
nebukadnezar
Rank 1: Thread
Nov 13, 2023, 07:33
I am not logging out; Could that be the problem why I'm hitting the rate limit?
Drake
Nov 13, 2023, 14:40
The login could trigger a rate limit.
Also, you said you're not logging out...but you're logging in again?
nebukadnezar
Rank 1: Thread
Nov 13, 2023, 21:00
Yes I forgot to code the logout because I'm coding a draft and understanding how appwrite works
nebukadnezar
Rank 1: Thread
Nov 13, 2023, 21:01
At the moment of writing, if I run my app once, it triggers a rate limit. It's been hours since I last tried to connect, so I'm utterly lost why this triggers so fast.
D5
Moderator
Nov 13, 2023, 21:02
Once time/request should not trigger rate limit 🤔
nebukadnezar
Rank 1: Thread
Nov 13, 2023, 22:07
I'm going through the code and trying to see and see a catch 22; sorry for the confusion!