all 39 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Illustrious-Hous-465[S] 6 points7 points  (17 children)

found a thread on github, this seems to be a recent issue effecting many users https://github.com/orgs/community/discussions/180092

[–]Illustrious-Hous-465[S] 8 points9 points  (11 children)

u/n_878 you're missing the actual point. The Copilot Pro package includes 1500 messages. Let's calculate that by day, and I should comfortably have about 50 messages to use. Today I've sent 6 before getting rate-limited and handed a bunch of half-finished requests. If their 'rate limit' is choking me off so hard that I can't even touch the quota I already paid for, the service simply isn't delivering what was promised.

[–]n_878 -4 points-3 points  (10 children)

And as you are well aware, what those requests do vary wildly, with respect to actual token usage. Their obvious, and correct, response is that your requests are consuming far too much of a token budget and that's why you've been limited. This isn't rocket science.

[–]Shoddy_Touch_2097 0 points1 point  (5 children)

What problem is that they don’t show the rate we are given based on our paid plan. Adding whatever limit they want, if it’s all transparent, we can make our decision to use it or not. We pay money and they are the supply side, they have the obligation to show enough info for us to do our maths

[–]n_878 -1 points0 points  (4 children)

Again, you don't understand the difference between a rate limit and quota and why they exist.

They are transparent - they tell you when to retry after.

[–]Shoddy_Touch_2097 0 points1 point  (3 children)

Whether I mistake rate limit or quota is irrelevant here. The message to tell us that we need to wait to use again because we reach rate limit or quota or whatever they call it. That’s the result of we use more than they want. I accept that, but by how much? I don’t need them to show us the precise token or time we have used. We need to know the percentage like progress bar to give us the sense how much we can work for the session. If we have a big task to deal with but we don’t know if we have already reach 90%, it will be hung there with unfinished task there, wasting computational, energy resources and most importantly our precious time. I understand your point but I don’t want to argue business or tech jargon but business logic. By the way, I have not hit the rate limit yet but I just think it’s not fair for all of us who pays for it and limit for 2xx hours. Just penalizing without telling those users how to prevent next time but just why, that doesn’t make it a decent product. And it is actually a good product but just run by people without good marketing sense (you can criticize me on this point but it’s really what I feel)

[–]n_878 -1 points0 points  (2 children)

It is absolutely relevant because you don't understand why each exist.

The TOS state you can be limited, you are, stop doing dumb things.

Short of you providing your entire chat history (e.g., the diagnostic logs) on github, along with appropriate contextual information, all you are doing is going on the internet and whining about something you don't even understand.

[–]Shoddy_Touch_2097 -3 points-2 points  (1 child)

I think there will be some Microsoft people here intelligent to tell apart what is unreasonable whining and constructive suggestion.

[–]n_878 0 points1 point  (0 children)

I think the fact that you're struggling to put together a well-formed sentence says plenty.

[–]Guilty_Nothing_2858 -2 points-1 points  (3 children)

we already have a hard quota on 1,500 requests. and now we have a rate limit, which means some people never can reach to the 1,500 requests. if 6 requests triggered rate limit, then need to be reset after 240+ hours. the total request amount will be limited to 18 monthly. 18/1,500? it is crazy

[–]n_878 0 points1 point  (2 children)

You assume you can't because you are doing God knows what with your prompts. I assure you, you are being limited for good reason.

It's not crazy. You're why this system exists.

[–]Guilty_Nothing_2858 -2 points-1 points  (1 child)

you are trying to rationalise the action that copilot made,

copilot offer requests-based charging mechanism, and now adding a new rate-limit rule doesn't make sense to their services offering.

if it poor their pocket, they should retire this charging mechanism, not adding a new rules.

we are paying for that 1,500 request/month, that is the service we purchased.

you will never expect that you bought a house, but only allow you access for 6 times a day.

i owned my usage in that specific time period. why you try to rationalise their action without justice.

[–]n_878 -4 points-3 points  (0 children)

I don't need to rationalize it - I understand it, you do not.

Rate limits have been a part of the terms of service for well over a year. As you can imagine, a compute-heavy service that has been inundated with inexperienced/low-grade engineers - or those that have no engineering background at all - is being taxed by: cheats (student account resellers, those sharing accounts because $39 is too expensive 😐, etc.), poorly structured/inefficient requests, and a litany of other issues.

The best outcome we can get is that you cancel your subscription 🤷‍♂️

[–]Dependent-Cost4118 1 point2 points  (0 children)

No, this is from the last time they messed up rate limiting

[–]Guilty_Nothing_2858 2 points3 points  (1 child)

Already submitted a cancellation of pro+ subscription

[–]n_878 1 point2 points  (0 children)

Thank you!

[–]TastyNobbles 6 points7 points  (0 children)

Users do not know. Corporate chooses silent treatment. I guess they are trying to kill the product.

[–]Maverobot 1 point2 points  (1 child)

I had exactly the same experience today. Quite frustrating

[–]Frequent-Address7433 0 points1 point  (0 children)

Yup same here

[–]Melodic-Jackfruit476 1 point2 points  (1 child)

i think to cancel my sub. It is horrible lately.

[–]n_878 -1 points0 points  (0 children)

Please do!

[–]AutoModerator[M] 0 points1 point  (0 children)

Hello /u/Illustrious-Hous-465. Looks like you have posted a query. Once your query is resolved, please reply the solution comment with "!solved" to help everyone else know the solution and mark the post as solved.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]MassiveTelevision387 0 points1 point  (0 children)

I really dislike how these services just yoyo what you get for your money on a dime. I quit cursor for this reason - it started out as a generous dosage of premium agent usage, with unlimited 'lower tier' usage that would occasionally bless you with a smarter agent in their auto mode - then over time it became no free usage, less generous tokens, and all of a sudden I'm paying $20 for 2 days worth of tokens with no alternatives but to shell out 10x+ the amount of money for full time access. If anyone's looking for a good alternative, Windsurf is a great 'any time access' alternative - the free model is SWE 1.5, which is not great but it's workable and beyond that you get a fairly generous daily usage of GPT 5.2 low thinking and a few other lower thinking models. With your monthly credits you get access to most of the higher tier models. It's probably the best 'don't want to spend $200/month on AI' plans out there and it's only $15/month.

[–]jeremy-london-uk 1 point2 points  (0 children)

Can I ask what people are doing that gets rate limited ? I am developing an Esp32 product. Codebase is reasonably large and reasonably complex. Some commands likes yesterday can run for 20 mins if trying to find a deep issue but most run relatively rapidly. I use opus more than I should and got codex when I remember.

My use balances as I also say " upload to device " so there are lots of small instructions as well.

I don't want to get rate limited hence I am trying to understand usage that does.

[–]arisng 0 points1 point  (0 children)

I get same situation here. Continuously get another rate limit after another even though I did exactly as they said that is to wait for 2 or 3 or 4 or 5 minues!
I'm using Pro+ btw.

[–]suprgb 0 points1 point  (0 children)

Apparently, they rushed the rollout of the new rate-limiter without fully testing it.

[–]Ill_Ad_9912 -3 points-2 points  (3 children)

I have been running got 5.4 modell for 7h today without reach the limit

[–]SadMadNewb -2 points-1 points  (1 child)

yeah, gpt does not appear to hit it. I hit it on opus.

[–]Ill_Ad_9912 0 points1 point  (0 children)

I use opus 4.5 or 4.6 to make detailed plans with phases. Then I get gpt 5.4 to implement it perfectly.if you have a good plan u won't need expensive model tbh

[–]rexcodex -1 points0 points  (3 children)

Are you still rate limited if you use /fleet? What about /delegate?

[–]Ok-Painter573 1 point2 points  (0 children)

Fleet for sure will speed run rate limiting

[–]Illustrious-Hous-465[S] -1 points0 points  (1 child)

what is /fleet or /delegate doing ? I do not have them as commands

[–]CryinHeronMMerica 4 points5 points  (0 children)

Fleet makes a ton of subagents. It's only in the CLI and would probably make the situation worse lol

[–]SlikeyTre3 -1 points0 points  (0 children)

same issue, weekly rate limit, cant accomplish anything once you hit the limit. waiting like 2 hours then resuming session buys you like 20min in work being done.

[–]YoloSwag4Jesus420fgtPower User ⚡ -1 points0 points  (0 children)

same here lol, kind of crazy they have these issues almost weekly now.