[Bug]: Front end progress not progressing after browser reload
Frontend Version
When you queue buncha jobs and reload the browser page with ComfyUI while the queue is still running then the progress information for all the jobs from before the reload is no longer showing / updating in the front end. Talking about the total percentages here only (workflow and node progress %).
Not a big issue. Right now it shows only in Browser Tab title from what I know.
Expected Behavior
Report and show valid generation progress after browser was realoaded.
Actual Behavior
When you reaload the browser page the progress information for the current job is not showing at all in the browser tab and for all the following jobs from before the reload it shows progress at 100% all the time.
Steps to Reproduce
Queue several workflow jobs and while the queue is still running reload the browser page. Observe incorrect progress reported in the browser tab title.
Debug Logs
n/a
Browser Logs
n/a
Setting JSON
n/a
What browsers do you use to access the UI ?
Google Chrome, Mozilla Firefox, Microsoft Edge
Other Information
From what I managed to dig out, the executionStore holds its own copy of the queue to provide its services.
The items are added to this internal queue by app.queuePrompt after prompt was submitted to server.
However, this front-end stored queue is lost when you reload page and neither app nor executionStore attempt to rebuild it after page is loaded.
Similarly the same applies if one is running comfyui from multiple browser tabs. Only the tab from which the prompt was queued will report progress information about that job.
This is minor issue but reporting it here in case it might shed light while investigating any other progress reporting problems in the future.
┆Issue is synchronized with this Notion page by Unito
Thanks, that's quite valuable information. You bring up a good point that it would be better if we just transmitted the information re: execution status directly from the websocket, rather than trying to have intermediate stateful store layer. Some of the other things you have diagnosed could be considered part of this larger issue:
- https://github.com/Comfy-Org/ComfyUI_frontend/issues/3377
Perhaps the solution for the above could also solve what you found here, so I added your issue as a sub-issue. Thanks again!