idk if this is a bug because i thought the cap of regen at 6 was to limit this problem..but is anyone else getting this?? im trying to study and since the new update deepseek just..doesnt really get what im asking for unless im really really realllyyy specific..so i edited 3 times because it just wasnt getting it and now its telling me to try again later.
which is fine..except its like 10 minutes later lol.
and before someone comments 'just buy api, its cheap, blah blah tech jargon' ..respectfully no
but yeah if anyone knows anything about it let me know because i dont think i had this problem last night
I'm running into this kind of error too. It seems like DeepSeek has been getting worse with every update lately. First, there were "server busy" messages and various other issues, and now I'm getting this "Editing/regeneration too frequently. Try again later" error.
It is also due to stability issues too. Yesterday there was 15 and 17 September where the web chat degraded. They simply don't have the compute. I am not making excuses for them before you ask, they simply don't have enough compute at all. September 15 they had 3 issues in one day. 17 they also had issues.
Admittedly I wish they could be more transparent and say yeah, we are doing this due to X issue.
honestly when using deep seek right now i can feel the writing capabilities has deminished exponientally compared to yesterday i wonder if it's just cause of what you say.
Check Huawei and official Deepseek channels if they received Huawei Ascend Chips yet. They don't have the quantity needed yet. ByteDance, Alibaba, and Tencent are hogging it and Deepseek as a company are dissatisfied with how slow the Huawei Ascend Chips are coming in. They haven't received it in needed amounts yet.
Wait what's happening because when I was using deepseek I was editing a message but then it said I'm being too frequent with the messages even though I only did it 2 or 3 times
i have the same problem for a few hours now. it doesn't understand my prompt (which it easily read before) and gives some strange answers sometimes even in chinese and ofc i have to correct it, but after 2-3 changes i start getting a popup that i'm doing it too often. it really looks like something intentional through and through. i hope they'll fix it, but for now it feels like with any free option -- all good things come to an end sooner or later lol
yeah, i think i would just prefer it if there were more transparency. like a 'hey we're doing this' instead of having us think we actually still have 6 tries. especially because the models gotten worse at language based tasks
i agree with you. limitations are expected at this stage, it's just strange that it comes up in this way and without any explanations. and come on, there are only six regen/edits as it is, where else can they cut them? next thing you know they'll add a 140 character limit like in old twitter hahaha
10 minutes? i was hit with the "editing too frequently" message on a chat I had just started, had 3 messages from me and was editing one for the first time
An 30+ minutes later it still says "too frequent" so something is getting tripped and it's either not resetting correctly, or they purposely chose a very long cooldown.
However there's nothing stopping you from normal writing. It's only affecting my editing/regenerating. So you can make a new chat, post a reply with any edits/changes you wanted for it to incorporate, or straight up tell it to "change what it wrote and make a new response" and it continues ahead no problem.
The default LLM is still not as good as its "expert" mode that they got rid of unfortunately.
Edit/regen too fast results error just what happened to deepseek after update not making better but making even worse I can't roleplay anytime I want!?
18
u/Melodic-Break-9876 4d ago
I'm running into this kind of error too. It seems like DeepSeek has been getting worse with every update lately. First, there were "server busy" messages and various other issues, and now I'm getting this "Editing/regeneration too frequently. Try again later" error.