It looks really strange, I’ve never seen anything like it before. You should check if you have any default values in these variables, or convert undefined to another value.
Another possible reason could be if you are using tag sequencing. This function often doesn’t work correctly and can cause bugs like this.
Thanks, @Alex Alex, for your reply.
Indeed, it was a situation with tag sequencing.
But it took me a while and some tests to find the problem.
Its very very weird, because with tag seq, event_id is really f*cked up.
Tag sequencing often breaks the parameters and sometimes the operation of the tags themselves, so I would recommend doing away with it altogether. It’s better to use an additional trigger on such tags and to set them to trigger priority.