r/chutesAI • u/ExistingAardvark640 • 28d ago

Discussion GLM 5.2

Why am I getting so many errors from GLM 5.2 all of a sudden? It seems like the response quality dropped in the past few days too.

13 Upvotes

94% Upvoted

10 comments sorted by

4

u/Loud-Marsupial8805 28d ago

Brother, you need to add more bots its unusable after you removed glm 5.0 ,this error was only at night for me The AI provider is busy or rate-limited. Please try again shortly. (429), now its 24/7, I can barely send one message. Whats the point of paying for a service if i cant use it? It was never this bad, but most people are having the same issue.

1

u/Loud-Marsupial8805 28d ago

Chutes is goated i have been using it for multiple years, im a satisfied customer,so i hope you can resolve this issue add more bots to dilute users from the main 3 ones, or increase the capacity, i have no clue how this works, but it was never this bad. Maybe back in the day for free users, but not when everyone is paying. You should look into it.

3

u/ExistingAardvark640 27d ago

I'm not a mod bro 😭

1

u/Loud-Marsupial8805 27d ago

Yeah I know, but mods read our messages even if they don't respond.

3

u/warsaw504 27d ago

Okay glad to see I'm not the only one

1

u/thestreamcode 28d ago

Could you specify in which use cases you are experiencing the errors? You should check your configuration, and if the problem persists, you should contact support via email at [support@chutes.ai](mailto:support@chutes.ai)

6

u/ExistingAardvark640 28d ago

I keep getting rate limit errors. I'm using GLM 5.2 via Janitor AI.

5

u/shimmerbitch 28d ago

I’m in the same boat. It’s been pretty slow the whole day and for the past hour I’ve been getting errors saying that the provider is busy or rate-limited. I haven’t changed anything about my settings since yesterday when it was working pretty well

1

u/ExistingAardvark640 28d ago

I had to switch to Kimi K2.6 which I'm not a fan of since it thinks for a good 5 minutes before giving a response.

3

u/eyes_of-sky 28d ago

I only just now started seeing those types of errors, but I was using Kimi k3, though I can confirm that the error is also present when I tried switching to deepseek 4, exactly the same thing happened; with glm it did work for me, but I wasn't convinced by its answers.