You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experiencing an issue that only comes right after starting Flower. Upon first loading Flower in my browser, I see the default view, which has a table displaying the workers. If I click on one of the workers, I am taken to the correct worker URL (/worker/...), but the page reports that "Unknown worker 'celery@...'". When I refresh the page in my browser, the worker information loads fine. I also found that refreshing the homepage before clicking on the worker will fix the problem.
To Reproduce
Steps to reproduce the behavior:
Deploy a celery worker and celery flower connected to a Redis broker
Open the celery flower homepage
Click on the worker in the "workers" table
You will see an "unknown worker" error
Refresh the page and the worker information will load
Expected behavior
A browser refresh show not be required to display the worker information.
Theories
I have a theory that this is caused by the startup order of the celery worker and flower. But I would expect that flower could gracefully handle being started either before or after the celery worker.
The text was updated successfully, but these errors were encountered:
This bug has been around for a very long time. First time clicking on any new worker gives Unknown worker. Any subsequent requests will succeed. Would love to see this fixed.
I am experiencing an issue that only comes right after starting Flower. Upon first loading Flower in my browser, I see the default view, which has a table displaying the workers. If I click on one of the workers, I am taken to the correct worker URL (
/worker/...
), but the page reports that "Unknown worker 'celery@...'". When I refresh the page in my browser, the worker information loads fine. I also found that refreshing the homepage before clicking on the worker will fix the problem.To Reproduce
Steps to reproduce the behavior:
Expected behavior
A browser refresh show not be required to display the worker information.
Theories
I have a theory that this is caused by the startup order of the celery worker and flower. But I would expect that flower could gracefully handle being started either before or after the celery worker.
The text was updated successfully, but these errors were encountered: