With a probing stream it appears that only the results linked to the oldest run time that produced it are kept in the database. For instance, the following results are available for a feature at Fri Jan 07 2022 15:00:00 after downloading multiple runs in the database:
forecast time - run time
Fri Jan 07 2022 12:00:00 - Tue Dec 28 2021 06:00:00
Fri Jan 07 2022 15:00:00 - Tue Dec 28 2021 12:00:00
Fri Jan 07 2022 18:00:00 - Tue Dec 28 2021 12:00:00
Fri Jan 07 2022 21:00:00 - Tue Dec 28 2021 18:00:00
Sat Jan 08 2022 00:00:00 - Tue Dec 28 2021 18:00:00
Sat Jan 08 2022 03:00:00 - Wed Dec 29 2021 00:00:00
...
We should find these results but also more recent ones in addition like the following:
Fri Jan 07 2022 12:00:00 - Fri Jan 07 2022 12:00:00
Fri Jan 07 2022 15:00:00 - Fri Jan 07 2022 12:00:00
Fri Jan 07 2022 18:00:00 - Fri Jan 07 2022 12:00:00
...
It appears that the values are correctly updated according to the latest run time but the run time is not updated and the first encountered run time is kept on each feature.
With a probing stream it appears that only the results linked to the oldest run time that produced it are kept in the database. For instance, the following results are available for a feature at Fri Jan 07 2022 15:00:00 after downloading multiple runs in the database:
We should find these results but also more recent ones in addition like the following: