Trigger action out of order

The menu says a trigger action will always issue the resultant keystrokes in order. I think I have found a case where they are not.

When triggered, I issue 2 commands in a row

  1. Update a global count
  2. Set a local bar, and local var has a restrict command so if set disables no.1 above.
    (The whole scheme is to limit updating of the global count to a one shot)

Whenever I add 2, number 1 will not even fire the first shot. I am stumped and any advise welcome.

There are some subtleties to the order things get resolved. Since I can’t see your whole piece definition I’m not 100%, but the first thing to try is reverse the order (among your traits) of your global property updating trait and your local (dynamic property) updating trait.