Good morning everyone,
since today, without having changed either the UI or the MCP Server, I receive an error whenever sendFollowUpMessage() from an UI component is triggered.
Since the console log doesn’t seem to produce anything meaningful, do you have any idea what recent changes might have led to this behaviour?
Thank you for your help!
Also have been getting this issue since today also.
I’ve tried switching between the legacy Apps SDK and the MCP Apps implementation, but both result in the same issue.
Yep - facing the same issue. Was working fine yesterday. Upon inspecting the console logs i saw:
”Error: web client getNodeByIdOrMessageId - no node found by id e9048537-edbe-4999-89e8-3451f27ffcdf isNodeStartWithPlaceholder: false”…….
The issue seems to be from openai’s end. From what I can guess it seems that a new conversation node is made when the widget HTML is rendered. This node is not commited to the internal react conversation tree and when the widget renderer tries to look for this node it does not find it.
Oddly enough, spamming “try again” seems to get it to work but it is definitely not suitable.
Good to know it’s not just me.
I tried it in a simple, small test app and got the same result, so at least I know it’s not cause of my implementation.
Hopefully they patch it soon.
Same here Content failed to load upon a click on widget button for a followupmessage @OpenAI_Support It would be great if you are able to check as it seems a common problem for many of us.
I am wondering if the day’s gonna come when ChatGPT Apps are finally stable and stop giving me headaches every other day. At least I am glad it’s not an issue with my code…
We are also seeing this issue in our development app
Hey all!
Appreciate you flagging this. We’re going to take a closer look and dig into what might be causing it.
In the meantime, if you’ve noticed any patterns, or other error messages, feel free to share. That kind of detail can really speed things up.
We’ll report back as soon as we know more.
hey everyone, faced this issue too, the main issue here is the parent node id not found which links to another issue: getNodeById Or MessageID no node found
what fixed for this issue for me:
deleting all the chats or majority of the chats where in which I was using this App
weird but hope this helps!
That might be suitable for the development environment – but it’s not a solution for customers who might use the app in production, assuming this issue also affects published apps.
Hey everyone, Can someone please confirm if this is still an issue. Our team will be happy to take a look and provide assistance here.
