Persistent outage in single chatgpt4 conversation, web client | OpenAI | Page 1

silent elbow · 2023-06-14T20:08:36.393Z

description: - one specific gpt4 chat returned this error after submitting a message, and every successive time for the last 14+ hours attempting to regenerate a response from said chat - the error cannot be reproduced on any other gpt3.5-turbo or gpt4 chat, which all appear to be functioning normally - the error message is attached - the chat itself is quite long, however the error message gives no indication that this is the reason for the error - being that this is a chat I use regularly for project development, it would be helpful to know if the issue is due to some sort of hidden conversation limit which is not disclosed on the platform, a technical issue, or something else

silent elbow Jun 14, 2023, 8:08 PM

#

description:

one specific gpt4 chat returned this error after submitting a message, and every successive time for the last 14+ hours attempting to regenerate a response from said chat
the error cannot be reproduced on any other gpt3.5-turbo or gpt4 chat, which all appear to be functioning normally
the error message is attached
the chat itself is quite long, however the error message gives no indication that this is the reason for the error
being that this is a chat I use regularly for project development, it would be helpful to know if the issue is due to some sort of hidden conversation limit which is not disclosed on the platform, a technical issue, or something else

cobalt vapor Jun 14, 2023, 8:58 PM

#

Can you open the network panel in the browser and show me the response failure (response headers and response itself) would be helpful

silent elbow Jun 14, 2023, 9:06 PM

#

Sure, here's the network console out:

_app-0df67bf7d9e6e732.js:14     POST https://chat.openai.com/backend-api/conversation 500
(anonymous) @ _app-0df67bf7d9e6e732.js:14
(anonymous) @ _app-0df67bf7d9e6e732.js:42
Z @ _app-0df67bf7d9e6e732.js:42
tb @ _app-0df67bf7d9e6e732.js:42
(anonymous) @ _app-0df67bf7d9e6e732.js:42
tf @ _app-0df67bf7d9e6e732.js:42
(anonymous) @ _app-0df67bf7d9e6e732.js:42
(anonymous) @ main-35ce5aa6f4f7a906.js:1
(anonymous) @ main-35ce5aa6f4f7a906.js:1
n @ main-35ce5aa6f4f7a906.js:1
u @ main-35ce5aa6f4f7a906.js:1
(anonymous) @ main-35ce5aa6f4f7a906.js:1
(anonymous) @ main-35ce5aa6f4f7a906.js:1
U.publicApiCompletionStream @ _app-0df67bf7d9e6e732.js:42
(anonymous) @ 734-30d5c00c7bdf11c1.js:1
(anonymous) @ main-35ce5aa6f4f7a906.js:1
(anonymous) @ main-35ce5aa6f4f7a906.js:1
n @ main-35ce5aa6f4f7a906.js:1
u @ main-35ce5aa6f4f7a906.js:1
(anonymous) @ main-35ce5aa6f4f7a906.js:1
(anonymous) @ main-35ce5aa6f4f7a906.js:1
(anonymous) @ 734-30d5c00c7bdf11c1.js:1
(anonymous) @ 734-30d5c00c7bdf11c1.js:1
(anonymous) @ main-35ce5aa6f4f7a906.js:1
(anonymous) @ main-35ce5aa6f4f7a906.js:1
n @ main-35ce5aa6f4f7a906.js:1
u @ main-35ce5aa6f4f7a906.js:1
Promise.then (async)
n @ main-35ce5aa6f4f7a906.js:1
u @ main-35ce5aa6f4f7a906.js:1
(anonymous) @ main-35ce5aa6f4f7a906.js:1
(anonymous) @ main-35ce5aa6f4f7a906.js:1
(anonymous) @ 734-30d5c00c7bdf11c1.js:1
(anonymous) @ 734-30d5c00c7bdf11c1.js:1
(anonymous) @ 734-30d5c00c7bdf11c1.js:1
(anonymous) @ 734-30d5c00c7bdf11c1.js:1
eU @ framework-e23f030857e925d4.js:9
eH @ framework-e23f030857e925d4.js:9
(anonymous) @ framework-e23f030857e925d4.js:9
re @ framework-e23f030857e925d4.js:9
rn @ framework-e23f030857e925d4.js:9
(anonymous) @ framework-e23f030857e925d4.js:9
oP @ framework-e23f030857e925d4.js:9
eF @ framework-e23f030857e925d4.js:9
ro @ framework-e23f030857e925d4.js:9
nU @ framework-e23f030857e925d4.js:9
nD @ framework-e23f030857e925d4.js:9
Y @ _app-0df67bf7d9e6e732.js:17
_app-0df67bf7d9e6e732.js:14 FatalServerError: Hmm...something seems to have gone wrong.
    at _app-0df67bf7d9e6e732.js:42:213357
    at main-35ce5aa6f4f7a906.js:1:106888
    at Object.next (main-35ce5aa6f4f7a906.js:1:106993)
    at n (main-35ce5aa6f4f7a906.js:1:107742)
    at u (main-35ce5aa6f4f7a906.js:1:107939)

#

I hope that is the information you're after, let me know if I can provide anything else.

I could also PM you the link to the conversation itself, although I would prefer not to do that if it isn't required

cobalt vapor Jun 14, 2023, 9:15 PM

#

the network tab in chrome would be better. with the specific failing request opened. here is some chrome instructions if you need them. https://developer.chrome.com/docs/devtools/network/

Chrome Developers

Inspect network activity - Chrome Developers

A tutorial on the most popular network-related features in Chrome DevTools.

silent elbow Jun 14, 2023, 9:46 PM

#

cobalt vapor the network tab in chrome would be better. with the specific failing request ope...

📎 message.txt

#

there you are

#

I hope that helps diagnose it better, appreciate your assistance

#

I'm presuming it's something to do with the conversation length or a disagreement with context fetching from whatever vector database backend you have storing conversation context outside of the embedding window.

Just a guess, since the input causing this error isn't at all unusual for the conversation, and its localised to just this conversation (not my account or my other chatgpt4 conversations in general)!

#

It's not mission critical to me that this conversation is salvaged, but it would be convenient. Mostly I'm interested in helping squash bugs because I like the product and am curious about how the system works in a more general sense

cobalt vapor Jun 14, 2023, 10:06 PM

#

can we move to DMs so I can get more information about this chat?

#Persistent outage in single chatgpt4 conversation, web client