ChatGPT Chat Pro thinking severely broken conversation state

What version of the Codex App are you using (From “About Codex” dialog)?

26.903.71938

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

ChatGPT Chat (non-Work) conversation 6a90b882-d884-83ed-b270-c8899ec417ba suffered severe state corruption across multiple front-ends and the back-end all at the same time.

I actually mean it. Conversation involving Pro thinking and cancellation went completely haywire. Before I realized that the system state was running into some kind of severe corruption, the chat started misbehaving across the web, desktop ChatGPT app, and Android app, throwing "Internal server error", and ultimately made me to spend many Pro thinking chat requests dealing with inconsistent and bugged system UX before I realized that the conversation is completely broken.

The behavior was indescribably nonsensical (which I nonetheless understand to be not a useful thing to report) but it ultimately resulted in concrete breakdown when the model produced 2 answers to the same Pro request, presenting inconsistent/conflicting information, and then the model was able to admit that it actually sees both answer. I think it has something to do with Pro requests being completely broken when they are canceled, but because of this indescribably broken behavior, I acted upon incorrect guidance in a computer game which ultimately caused losses that are not model's direct fault.

More severely is the fact that ChatGPT on android, on Windows desktop, and on the web, are suffering their own share of corruption; on Android, the conversation is perpetually stuck in model appearing to be working, and a message being stuck in "Waiting to send". On Windows desktop, the conversation presents empty page, no messages. On the web, I was unable to resume the conversation for a while with "Internal server error".

The behavior of the linked conversation made no more sense to me than this report probably will to its future reviewers. That is a very severe product issue in itself, don't you think?

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a08ad8-ca98-77e0-aa20-16735e939245

What is the expected behavior?

No response

Additional information

Feedback ID has "no-active-thread" which suggests to me that the issue is even more severe, because I sent bug report from having the conversation opened, even if it showed no content.

Start with feedback ID no-active-thread-01a08ad8-ca98-77e0-aa20-16735e939245 and conversation 6a90b882-d884-83ed-b270-c8899ec417ba, then compare the cancellation behavior across the web, Windows desktop, and Android clients. Done should mean the failure can be reproduced and the conversation state remains consistent across clients after a Pro thinking request is canceled.