Example (without bug):
User: Give me an idea for a bug-eating machine.
ChatGPT: How about the Supreme Bugeater 3600? etc etc
User: Tell me more!
ChatGPT: It also has a love for crunching on walnuts. Easy on the walnuts!
Example (with bug):
User: Give me an idea for a bug-eating machine.
ChatGPT: How about the Supreme Bugeater 3600? etc etc
User: Tell me more!
ChatGPT: Let’s do the Amazing BugEater! etc etc. It also has a feature where it eats cake!
(interperets it as:
Give me an idea for a bug-eating machine.
Tell me more!)
Yeah, this bug has been happening intermittently for over a month at this point. Probably closer to two months, actually. Great example, by the way; I feel like OpenAI could use a Supreme Bugeater 3600!
I put together a list of posts about this issue here:
Maybe it’ll get someone at OpenAI’s attention, or at least give them a good idea of exactly what the issue is.
I’m seeing that too, and it’s getting really frustrating, I’m writing stories on chatgpt, and then when I log off, the previous prompts I send are glitched and merged with previous ones, and the response is missing, and then edited ones are then duplicated and sent out like i sent the same thing numerous times, any way to fix this bug:
example:
user: the vehicles hit each other
chatgpt: the cars catch fire
user: the fire station arrives
chatgpt: the fire station saves the day
when I log off and come back, the bug appears:
user: the vehicles hit each other
the fire station arrives
the prompts i send are glitched together, and I can’t edit them
any way to fix this annoying bug?
The fix is only temporary but you would have to reload the page every time you make a prompt and a response is generated and see if it saved. I have had this bug for about 1 month now and no fix.
Unfortunately this doesn’t always work, at least not for me. Even if the most recent response stays after reloading, it can still disappear after sending the next prompt. And some disappear only after logging out and logging in again.
I’m not sure if OpenAI realize what a bad look it will be for them if this bug is still happening whenever they release the next big iteration of whatever model ChatGPT is using.
I mean, if you haven’t encountered the bug before, it’s very easy to assume that it’s a problem with the model itself when you first encounter it, even though in reality it’s much more likely an issue with the message delivery/saving system.