Incorrect labeling of jobs

[acampove]

Hi,

In the newest version there seems to be a bug, in the dashboard I see:

but in the terminal I see:

i.e. the done jobs seem to have been moved to running, so none of the jobs appears as done.

[acampove]

I would also add a Failed, Idle and Held counter.

[acampove]

And another thing that I just noticed, when one job fails, all of them seem to be registed as failed, i.e.

2026-07-07.14-34-09.mp4

this wasn't like this before and it makes it harder to find the jobs that actually failed in order to check the trace and fix them.

[zhanghaomiao]

Hi, you're still using v2.0.7. Could you see if the same issue occurs in v2.1.0?

[zhanghaomiao]

From the video you upload, in the DAG, the total number of jobs that need to be run is the sum of the job counts for all rules. So the total number of jobs is 17,081, which is correct, I will debug the running count.

[acampove]

@zhanghaomiao yes, both problems still appear in v2.1.0. I think it might be about the dashboard in the container rather than the python plugin.

[zhanghaomiao]

Hi @acampove, thanks for checking.

Flowo v2.1.1 has been released for both the server/container and the Python plugin.

The “all jobs become failed” issue should be fixed. The cause was that, when a workflow closed, jobs still marked as RUNNING could be incorrectly changed to ERROR if another job had failed. They are now marked as UNKNOWN instead, unless Snakemake reports an actual job_error.

For the “done jobs appear as running” issue, I could not reproduce it in my tests. Could you please provide a minimal demo workflow or reproducible case for that part?

[acampove]

Hi @acampove, thanks for checking.

Flowo v2.1.1 has been released for both the server/container and the Python plugin.

The “all jobs become failed” issue should be fixed. The cause was that, when a workflow closed, jobs still marked as RUNNING could be incorrectly changed to ERROR if another job had failed. They are now marked as UNKNOWN instead, unless Snakemake reports an actual job_error.

For the “done jobs appear as running” issue, I could not reproduce it in my tests. Could you please provide a minimal demo workflow or reproducible case for that part?

@zhanghaomiao I made a mistake, I was again using 2.0.7, It seems that I had to:

• Clear the cache in my browser
• Use the 2.1.0 version explicitly, because the latest one was pointing to 2.0.7. Now I see that it points to 2.1.1

I see now the dark mode (looks very nice, thanks) and I see that other things seem to have changed too and I am testing it right now.

Cheers.