The endpoint /runs seems to return the job list creation time, instead of when the experiment run started

[kinow]

Hi, in a20x (ClimateDT) I issued an autosubmit create at 10:34 (unfortunately Autosubmit logs are not including the timestamp -- they should, IMO).

$ stat ../conf/metadata/experiment_data.yml
...
Access: 2024-12-23 12:03:53.634919297 +0200
Modify: 2024-12-23 12:03:43.598537000 +0200
Change: 2024-12-23 12:03:43.598537000 +0200
 Birth: 2024-12-23 11:34:55.237694168 +0200

And I executed the nohup autosubmit run > logs... command at 10:44.

$ stat nohup_a20x_20241223114434.log 
...
Access: 2024-12-23 11:58:06.697704067 +0200
Modify: 2024-12-23 12:05:17.956131188 +0200
Change: 2024-12-23 12:05:17.956131188 +0200
 Birth: 2024-12-23 11:44:34.983779385 +0200

While talking with @GinkaVanThielen and trying to locate an endpoint with run start/end times, I found this one when visiting the experiment configuration page, https://HOST/v4/experiments/a20x/runs

The response for my experiment a20x is

{"runs":[{"run_id":1,"start":"2024-12-23T09:34:55+00:00","finish":null}]}

Which is incorrect. The start of my run was at 11:44:34 (or around that time, once Autosubmit parsed/validated/loaded everything for the run). Looks like the API is returning the create time of the jobs metadata or sqlite DB. In either case, that could have been done days/weeks before the experiment is actually submitted.

[LuiggiTenorioK]

The start date is directly retrieved from the DB. IMO I think Autosubmit should not write the start date when doing autosubmit create since in the experiment_run table we already have a created column.

PS: There is another thing in that experiment_run table. Why do we have 2 different datetime formats for created, modified, start, and finish? Why created and modified are not time zone aware?

[mcastril]

Good point, we should have uniform formats for the dates