Generate Button in new Image UI is permanently disabled
In the new image generation UI, the “Generate” button is permanently disabled after I’ve generated a new image. This persists after reloading the page and on different devices. I still have 100% usage limit left. It also doesn’t change when I select another image model. There is no feedback as to why the button is disabled.
Log in to comment and vote
Comments5
Moccasin Croissant
Yes, the bottom button in the new image generation UI sidebar. I am able to use image generation in the regular chat mode without problems. No image generation has been in progress for a couple of hours now.
The good news is: The issue has resolved itself. I clicked around in the UI (resolution, aspect ratio, model selector), added and removed text in the prompt and all of a sudden, the button became clickable again. It also remains clickable after generating a new image (that’s what previously happened: the button showed the loading spinner and became disabled, then the loading spinner disappeared but the button didn’t get enabled again).
So for now, that issue is resolved. Thanks for your fast response! I’ll let you know should the problem re-appear in the future.
Mark Florkowski
Got it! Glad to hear it is resolved now. It seems like maybe one of the controls got stuck in some bad state and was blocking the generate button from being enabled. If you do encounter this again, definitely reach back out!
Moccasin Croissant
Since this is happening on three different browsers, I doubt this is browser-related. Presumably my account is in a bad state? Anyway, clearing caches, cookies and logging in again doesn’t change anything. Also a new private browser tab doesn’t fix the issue.
Mark Florkowski
Ah sorry I missed the multiple devices on my first read.
Do you have any active generations in progress? does editing the text prompt make any difference?
To clarify, this is the button in the sidebar that you are referring to, correct?
Mark Florkowski
I can’t seem to reproduce this. Can you try clearing your cache and cookies and logging back in to see if the issue persists?