I have seen similar rate limit errors even when usage was low, and in my case it was tied to background sessions and cached conversations. Starting a completely new session or logging out and back in sometimes cleared it. Might be worth trying if you have not already.
No comments yet.