The time when I changed the flags was Feb. 28 10:26 to 12:48 in case that helps with tracking down which data is affected.
@chaen what can I do to help from my side?
We did raise & discuss this issue in the OPG of Feb 20, but not in the context of ongoing processings.
Sorry, I probably had to give more details in the warning about "side effects" of this flag...
Argh, that's bad
I had not understood that it was for 2024 data, I thought it would start in 2025....
We're not testing. Flags for 2024 data are still not finalized. What you probably saw is the transition from UNCHECKED to CONDITIONAL for all runs ...
Could you please refrain from testing on production data on which we are currently running processing campaigns ? This fucked up at least one of ou...
-
df7f4370 · Add release v11.0.61 to releases.cfg and CHANGELOG
-
2c7834bc · Update versions and changelog for release of v11.0.61
-
ce5f8f5d · Add release v11.0.60 to releases.cfg and CHANGELOG
-
82e53d78 · Update versions and changelog for release of v11.0.60
I am closing the issue then.
Thanks for the quick fix @azhelezo! Everything works as expected now....
The first was my mistake... I have not updated DB after MR was merged, so the flag was not there yet....