In the context of the Big multi-user workflows sprint, we will come up with more dynamic ways of deciding whether a workflow should be started or not.
This will make users wonder why their workflows take long to be queued. This new page is intended to give users information about whether the cluster is busy, so they can relate to why their workflows take long to be scheduled.
In the context of the Big multi-user workflows sprint, we will come up with more dynamic ways of deciding whether a workflow should be started or not.
This will make users wonder why their workflows take long to be queued. This new page is intended to give users information about whether the cluster is busy, so they can relate to why their workflows take long to be scheduled.
Steps:
Note:
status.py
in RS which could be extended for this case