john w

Thanks for the detailed report, and sorry for the trouble. We found the cause: if a file is uploaded with the same name as a file previously moved to Trash, its storage record can remain marked as Trash and block the public media link needed for generation. We have prepared a fix, but it is not live in production yet.

We don’t have a confirmed timeline yet for Story continuity or video-generation consistency improvements. These remain separate issues under investigation. If either problem recurs, please share the conversation link or approximate time and, for video issues, the selected video model. Screenshots are not required; this

We don’t have a confirmed timeline yet for Story continuity or video-generation consistency improvements. These remain separate issues under investigation. If either problem recurs, please share the conversation link or approximate time and, for video issues, the selected video model. Screenshots are not required; this

Thank you for the update. I appreciate the model change and the clarification that Story continuity and video generation are being investigated separately.

I’ll test the updated Assistant model and monitor whether the instruction-following and back-and-forth issues improve. However, I’m still concerned about the broad

Yes. Files moved to Drive Trash remain recoverable for 7 days and are then permanently deleted automatically. You can restore them at any time during those 7 days.

One important detail: the files in Generated are the original generated images and videos, not duplicate entries. Deleting an item there removes the actual

Thanks for reporting this. “Positive Prompt is required” was an internal image-tool validation message and should not have appeared while using Story mode. You did not need to provide a separate positive prompt—the Story assistant should supply it when calling the image model.

We’ve updated the image-tool instruction

Thanks for flagging this, and sorry this blocked your render. We confirmed the issue and fixed the video request so the supported output format is now supplied automatically—there is no MP4/WebM field you need to find or complete. We also verified successful video generations after the fix. Please refresh GizAI and try

Thanks for the detailed reproduction. Story and Chat were using a different local-file path from the working Video uploader, which caused authenticated uploads to fail before the message was sent. They now share the same media upload contract, and the fix is live. We verified that an authenticated image upload returns

Sorry about the interruption. This was a temporary service issue, and access has been restored. We’ve confirmed that chat, story/image, and video creation are working again. Please refresh GizAI and try once more. Thank you for reporting it.

Me too. Is there some kind of issue with the new update to the site or something?

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