#Image & Link Rendering Gets Stuck If Chat Is Left Idle or If User Returns to Wrong Chat (Impacts Lon

1 messages · Page 1 of 1 (latest)

barren caveBOT
#

Reported by @inner quail

Bug Report: Image & Link Rendering Gets Stuck If Chat Is Left Idle or If User Returns to Wrong Chat (Impacts Lon
`Steps to Reproduce`

Generate large post — images (maps, RPG books), and/or links (multi-part content).

Chat shows "Rendering..." or "Working...".

Leave chat idle (sleep, work, or while multi-tasking / doing map corrections or working in other tabs).

Sometimes return to chat after forgetting which chat was active (natural in long creative sessions).

On return — image render and/or link fails — post lost — chat may freeze or clog.

In some cases, I accidentally added more instructions or posts to the wrong chat,

`Expected Result`

Images and links should auto-send to chat as soon as rendering/uploading completes — regardless of whether user is active or idle.
If the render or link expired, system should show a clear message and allow easy re-request — avoid silent failure.
System should support natural creative flow — multi-tasking and accidentally returning to the wrong chat should not break results.
Chat should handle this gracefully without clogging or freezing.

`Actual Result`

ChatGPT web app (chat.openai.com), Edge browser (latest), UK region, Plus (GPT-4o). Workflow: long-form RPG sector maps, chronicles, military/economic breakdowns, multi-image + link structured posts. Creative flow spans multiple chats; issue reproducible across multiple sessions.

`Environment`

ChatGPT web app (chat.openai.com), Edge browser (latest), UK region, Plus plan (GPT-4o). User workflow: Long-form RPG sector maps, RPG books/chronicles, military & economic breakdowns, multi-image + link structured posts. Creative flow includes working across multiple chats — normal for this type of user. Issue reproducible across multiple sessions.

#
Additional Information

Please provide relevant details to help resolve the issue, such as:

  • ChatGPT Shared Link (if applicable).
  • Screenshots or videos demonstrating the problem.

-# ➜ Need to contact support? Visit the OpenAI Help Center.

inner quail
#

**Hey — just leaving this here for feature request.
I do big maps and worldbuilding stuff (TTRPG, sector maps, structured posts).
Sometimes I leave the chat running while it’s rendering, or I’m off fixing a map, or I forget which chat I was in.
It would be great if images and links just auto-sent when ready — even if I wasn’t sitting there watching.
Right now ChatGPT seems to think it can auto-send, but if I leave it too long, it sometimes gets stuck and breaks the post.

Also — sometimes the AI says “Stay in this thread” — but honestly, with my workflow, I can’t always do that.
I’m switching between chats and fixing things while I wait.
Auto-send should still work even if I’m not sitting in that one chat the whole time.

Would be really helpful for big creative workflows like this.
Thanks!**

#

Also — I can see this bug happening live right now in my "Protectorate Map Update" thread.
I left ChatGPT working in that thread (barely spoke — just letting it render), while I was switching chats to map out this bug for you.
Now that thread won’t render properly — it’s stalling — even though I was doing exactly what it said (leave it to work).
So this bug happens even if I’m doing things “correctly” — leaving it idle — it still breaks if I switch chats.
That’s why auto-send needs to handle this better.

#

Also, just noting — right now in my "Protectorate Map Update" thread, the AI still thinks everything is fine — it’s “working” — but the first render cycle stalled.
It looks like auto-send logic failed silently after I switched chats.
Even though it didn’t show an error, it’s stuck — this is why it’s hard for users to know if something broke or not.

inner quail
#

“This is a known platform image handling bug, not AI loop.
I was pushing a very large RPG sector map with many fine vector layers and transparent blends.
The first chat failed due to external link rejection → second chat triggered UX loop flag because of repeated platform upload stalls at ~92–93%.
AI confirmed it was NOT regenerating or looping — was stuck on image complexity.
Now running correct fallback flatten pass — this is helping the devs isolate the edge case for large map workflows.”

inner quail
inner quail