By that logic, wouldn't the signal event just run forever? If it's every tick, why stop after 1 second?
I think we're focusing on the wrong part of this. I'm not worried about the signal part - it's the wait command that seems to be causing problems.
The CAPX says, "On the start of this layout, wait 1 second, send a signal."
Every other Construct command in a "Start of layout" trigger runs only once. I updated the CAPX to show that.
But for whatever reason, in this CAPX, sending a signal after a wait command runs X times - sending X signals - where X is the amount of ticks we waited before the send action.
Don't you think that's weird?