I asume Rui made a very good point with his previous posts.
It has happened before that the (Hardbytes) PyCan library changed the position of the actual message in it’s Can-String.
You won’t notice any difference in the canlog, because this is being saved directly using Pican modules (Say; Not using Python).
I can / will check this next Tuesday. I saw there should be a can.message() -like function now, which makes it no longer needed to cut a substring from the full detail output..