■■■■ was running nice for awhile, now back to conversation too long errors again -.- What happened? ha
Just started getting this again
I just started getting this again
Guys… how did you make this worse? I went through ONE round of 25 agent responses.
One round, which was fairly complex and will make it a bit of a PITA to spin up a new agent so I’ll just dump to commit. Doesn’t stop you from charging me those AI credits.
1 Like
I’m having this same bug now with even short new chats with not much context.
This error ■■■■■! At least give a warning.
1 Like
This is back
having the conversation too long issue again in 44.10
Yeah this is back.
Totally understand we’re just out of the holidays, and look forward to more QOL fixes in the coming weeks.
1 Like
i hope it get sorted soon
1 Like
dont know if it’s related it moved from the “too long” message to permanent … … …
Hey everyone,
It seems a few people are facing this again, so I’m raising internally to see whats going on. Watch this space, will get back to you soon!
4 Likes
I’ve been facing this issue over the last few days. I’ve tried building two different apps and after about 20 prompts using 3.5-sonnet I get “Your conversation is too long. Please try creating a new conversation or shortening your messages.”
When I swap over to 4o I get the same message 
We think we’ve identified a cause for this, and we’re just releasing a fix on our backend which should be available in a few minutes.
Please let me know if you are still seeing this repeatedly, and we can dig in further!
1 Like
@danperks Unfortunately, I’m still getting that error. I got about 60 prompts into a new project and then tried to switch to agent mode then I got the message. I ended up restoring to previous version and then was able to continue.
i am getting still same error. i can’t continue on my project which i used same agent context from beginning and until 3 days ago worked really well.
I also believe there is a relationship between composer submissions and these errors
Starting a new project from scratch is fine
let that project build a few prompts and bang
I’ve got an even more fun version now where I’ll be in the middle of a delicate operation and the agent ghosts me. Three dots, generating, and then the chat springs back to the bottom, awaiting submission.
Somewhat desprate not to loose time onboarding a green composer, I waste time closing, restarting, and submitting in combination a few times until I give up and start from scratch, sometimes dumping to a commit rather than risk an untrained agent going hog wild on my code but not wanting to spend 5x longer doing it myself.
Pretty frustrating behavior.
I can confirm this above action, too!
So I tried
Opening a new composer imported cursorrules etc
looked good
was refactoring a single API endpoint and when the agent starts assisting, it gets partially done. Then this
Followed by this now
If the problem persists, please check your internet connection or VPN, or email us at [email protected].
Yeah I’ve been getting this issue way more frequently in the last couple of days.
Having to restart the conversation and fix the mess that happens at new conversations is just so discouraging…