#Upgrading to Premium broke all my previous conversation

84 messages · Page 1 of 1 (latest)

vocal inlet
#

Bug Report:

Steps to reproduce:

  1. Upgrade to Premium with credit card
  2. Start a new conversation using premium UI
  3. Change to an old conversation
  4. Type and send a new prompt in that conversation

Expected result:
ChatGPT answers as it normally does

Actual result:
Error message is displayed "Try refreshing your browser."

Additional information

Browser: Chrome latest
OS: Win 10

Logging out and in doesn't seem to fix the issue. It happens in all old conversations from before Premium. New conversations after Premium work OK.

image.png
#

posting this screenshot from @steel kettle who also has this error (along with a large number of users)

#

also happened to @red moth @pastel depot and @brisk vessel as well

feral whaleBOT
vocal inlet
#

also happened to @red moth @pastel depot

fervent lake
#

Also happens for free users

vocal inlet
#

thanks @fervent lake

quiet salmon
#

Happens to me as well.
I have one old conversation that seems to work fine though.

red crater
#

Same here... Everything was working fine last night. If the system is overloaded I wish they would say so instead of "try refreshing your browser."

red moth
#

I've tried clearing cache and using different browsers, but that didn't fix it

solid mantle
#

Same. Paid and now my chats are locked.

steel kettle
#

Yeah I think new conversations work but the old ones don’t

dusky laurel
#

For old conversations they left a very important param blank (The model param on the conversation API). It's a silly mistake, but fortunately should be quick to fix.

placid mica
#

SAME !!!

red moth
viral cedar
#

same here guys

#

should we cancel until MOnday?

vocal inlet
#

@viral cedar we should definitely do something like that

vocal inlet
#

@fast gust @tight vine can you guys say something? do you check bug reports? who is in charge of checking bug reports?

feral whaleBOT
#
<:attention:1046329820331646986> coiki#6683 said:

@hot kiln is the team working on the weekend?

||653205565803200524||

OpenAI staff mentions are disabled.
vocal inlet
#

wow

#

pfff ChatGPT is still in a lucky position, but now they're a paid service now and with competition like Google

solid mantle
#

Yeah it's pretty scummy to launch your paid product on the weekend and forget about it until monday

vocal inlet
#

if this bug is affecting 100% users I would be fired, as a product manager

#

like immediately

#

leaving for the weekend with such a bug in production...

#

what's their QA process

viral cedar
#

try an new disccussion

#

comback let me know, it worked for me

red moth
viral cedar
#

yeah true!

golden thunder
#

Maybe it will be probs few days

#

Imagine asking many many many times

red crater
vocal inlet
#

especially if it's as simple as what @dusky laurel mentioned... maybe it's not but maybe it is 🤷‍♂️

placid mica
#

Unless something unexpected happens, it looks like we'll have to wait until Monday before we can expect any substantial updates on the issue at hand.

vocal inlet
#

🥲

#

Monday here in Japan now

#

let's see

young lake
#

same here

vocal inlet
#

Monday and it's still happening

image.png
quiet salmon
#

Let's wait at least until tomorrow, it's almost midnight at San Francisco.
Hopefully they'll get it sorted in one day.

vocal inlet
#

it seems like they're having another large issue: when the new premium algorithm (turbo, I believe) is used. we're receiving answers from other users

heavy pollen
vocal inlet
#

yeah check the other thread, it's crazy

vocal inlet
misty iron
#

There are a lot of threads with this same error!

fresh brook
#

A response would be nice. You probably shouldn't accept money from people if you can't offer some level of customer service to them. A ticketing queue... anything is better than nothing.

paper elk
#

Can someone with this issue post their payload from the conversation network request and the response from their models network request?

vocal inlet
vocal inlet
feral whaleBOT
#
coiki#6683 said:

@paper elk would this work?

||653205565803200524||

OpenAI staff mentions are disabled.
vocal inlet
#

oh

#

can't mention

#

that's the POST to conversation endpoint

#

then it seems like I receive an object, which is the error

paper elk
#

it looks like you're looking at the console - check out the Network tab instead

vocal inlet
#

oops, my bad

#

here it is:

#

{"action":"next","messages":[{"id":"f39765ee-58fe-446a-b44b-7f3a9adf3db7","role":"user","content":{"content_type":"text","parts":["test"]}}],"conversation_id":"91e77777-2cd6-4c1d-8e2e-4200d0272f1b","parent_message_id":"eb9dfa82-d5dc-4722-b77b-d4ed4c4f39bd","model":""}

#

Conversation endpoint

#

I don't see anything tagged as models when I type a question, should I go to another page?

image.png
paper elk
#

give the page the 'ol refresh

vocal inlet
#

on it

#

response from models:

#

{"models":[{"slug":"text-davinci-002-render-sha","max_tokens":4097,"title":"Default","description":"Optimized for speed, currently available to Plus users","tags":[]},{"slug":"text-davinci-002-render-paid","max_tokens":4097,"title":"Legacy","description":"The previous ChatGPT Plus model","tags":["concise"]}]}

#

excuse the lack of format

paper elk
#

no problem. this helps a bunch. ty!

vocal inlet
#

thanks for getting back to us! 🙏

paper elk
vocal inlet
paper elk
vocal inlet
#

I worked with ML to plan delivery routes, much different I imagine

vocal inlet
mellow basin
#

I noticed that all the conversations from the free have the default model selected, but that is the PLUS now for me, they should be on legacy, is that causing the problem?

vocal inlet
quiet salmon
#

Yes working now for me as well 😊