Autosubmit exp_db_manager returns RUNNING for workflow that has completed
Hello @dbeltran
Autosubmit Version
Dev, using rocrate
Expid affected(If applicable)
NA
Which task has issues? Where is the log(If applicable)
NA
Summary
I am running an mHM experiment that is completing successfully. I can run autosubmit monitor a008
and I get the correct plot.
However, in my RO-Crate file I get the status of "PotentialAction", which means the workflow has nor failed, nor succeeded. Checking with the debugger, I am getting a RUNNING
for the call exp_db_manager.get_experiment_status_row_by_expid(expid)
.
Looking at the as times DB, a008 is indeed shown as RUNNING, even though it has completed:
@dbeltran shouldn't the status be updated to COMPLETED?
Is there another way to programmatically access the workflow execution status?
Thanks!
Steps to reproduce
Run any experiment that completes successfully.
What is the current bug behavior?
Status shown as RUNNING for a COMPLETED workflow.
What is the expected correct behavior?
Probably store COMPLETED or another status that means success in the DB.
Relevant logs and/or screenshots(if applicable)
Above
Any other relevant information(if applicable)
()