Ich habe mir jetzt extra für über 200 € die Pro-Version geholt weil ich dachte dann ist es besser. Aber der Fehler kommt nach wie vor. Ist mega ärgerlich und ich verstehe nicht das es keine Lösung gibt
The o3 getNodeByIdOrMessageId is likely caused by part of your custom instructions.
- Switching them off fixed the issue for me.
I also have the same problem. This error removes last prompt and output so it’s extremely annoying.
I’m thinking of switching to the other AIs.
I also have this bug everyday and its unacceptable in a subscription product. And this was reported what 3 months ago? Fixing this kind of thing should be priority.
If it’s a long context it’s a context break unfortunately only ha6uk plausible way to deal with it by creating a branch of the same interaction with a shared link.
It’s August now, and I still get that error regulary too:
getNodeByIdOrMessageId - no node found by id: placeholder-request-68906b8b-4eb0-8323-a832-ee0d7672a440-70
It shows up mainly on longer conversation, but it depends what you except as “long”. Sometimes it already pops up on a conversation which I am having for some hours with, lets say, 5-10 answers.
It seems to trigger more if I am uploading files more often.
This is annoying.
It’s October, and I’m getting this error regularly as well. It’s mostly on the Windows app but happens on the web app as well. Furthermore, it happens when the conversation becomes a bit long, and then it does not display the response until you refresh the app, or close it and reload. It then keeps on happening every 2–3 questions with much the same result. Asking another question re rolls it into the previous prompt. This is an extremely annoying bug.