I can report other bug like this if you want.
In the topic “channel.prediction.lock”.
The “locks_at” is never the date on which the prediction was actually locked. It is automatically set to the initial scheduled lock date.
Reproduce :
Launch prediction for 2 minutes
Lock the prediction prematurely after some seconds or 1 minute if you want.
the locks_at in the lock event is the initial datetime + 2 minutes and not the real locks date