john w

Hi John, sorry for the trouble. We found and fixed the Story issue that could leave an old attachment/image reference attached to a later text-only request and cause the “Attached file reference is missing or invalid” error. Please try the Story flow again now. Thanks for reporting it and for your patience while we tr

Hi John, thank you for reporting this. We investigated the upload and Story attachment flow around your recent reports and found that files could fail before they were fully attached to the chat or Story request. That could make the conversation appear to stop, or show an upload-related error even when you were only tr

Hi John, I saw this earlier upload report as well. We handled it together with your newer Story/chat upload post. The attachment/storage path has been updated so local files uploaded from chat or Story should now reach storage correctly and appear back as attached files before generation starts. File chips should also

Hi John, thanks for the detailed report. I checked the affected chat and the later runs from your account. The confusing part here was the error message: some requests were being blocked by content policy handling, but the chat could show that as a generic generation or file-format error. We updated that handling toda

Hi John, I saw this duplicate report as well. We handled it together with your other Story upload post. The Story-specific image attachment path in the app has been updated, and your later test appears to have accepted an attached image. Please retry your Story workflow with the reference images you want to keep.

Hi John, thanks for the detailed report. We checked the Story-specific image path in the app and found an issue in how attached images were being passed into the Story flow, even though the general video upload path could still work. We have updated that path so attached Story images are handled through the working te

Hi John, sorry you did not get a faster reply here. I checked this together with your earlier post. Your account and access look fine. The problem is most likely model fit, not your subscription. GPT-5.4 Nano is fast, but it is not reliable enough for long story projects with locked canon, exact formatting, images, an

Hi John, sorry this has kept interrupting your story work. I checked your recent sessions and your account access looks fine. This is not a subscription problem. The main issue is that the model you were using is not strong enough for the kind of long story workflow you are doing. Long canon, exact character details,

Hi John, thanks for reporting this. I checked your recent video attempts, and your account access looks fine. Video generation is working, but some recent attempts were blocked by the safety filter, and one video job was left showing as processing instead of closing cleanly. We have updated the video job handling so c

Hi John, thanks for reporting this. I checked the recent session, and your account access looks fine. This does not appear to be a subscription issue. What you are seeing is likely the model steering a sensitive creative-writing scene toward safer, more general wording. That can make it feel like the chatbot is taking

Hi John, thanks for reporting this. I checked your recent sessions, and your account and image generation access look fine. This does not appear to be a subscription issue. The issue is that some smaller/faster models are not strong enough for this kind of AI Story workflow. In particular, GPT-4.1 Nano is weak for na

Hi John, thanks for reporting this. I checked your recent AI Story session, and your account and image generation access look fine. The issue appears to be that the model continued the narrative but did not reliably follow the tool-use instructions needed to attach images and choice buttons. GPT OSS can be very fast,