A long time ago a project had an issue that some data attached to events was getting lost and not received by other FSMs waiting for the data.
I solved this the first time by using "set properties" instead.
When the bug appeared for some of the events using properties, cutting a rather larger FSM into smaller pieces solved the issue.
It seems that PM doesn't handle well event related operations coming in big waves from a single source (FSM).