Coming back to this locks_date problem, I think this is actually not intended at all.
The “channel.prediction.lock” event returns a “locks_at” while “channel.prediction.end” returns a “locked_at”. Each time the information is wrong. None contains the real locking date but only the programmed one when the term has changed as if we wanted to talk about the past.
“locked_at” is really self-explanatory though.