Orgainzed event actions on button in perspective

[justinedwards.jle]

This has come up several times. The various scripts run asynchronously, so there's no guarantee they will finish in a specified order.

Changing tag values on click action

Your navigation action is navigating away from the page and cancelling your script. Actions are started in order but are executed asynchronously; they do not wait for the previous to finish before running. Script actions have to be sent to the gateway and are thus the slowest to run, and I believe they’re terminated if the owner is closed. I actually started a topic about this exact situation

Component action numbered order is deceptive for inexperienced users

I recently had a question from a colleague who is fairly new to Ignition about why his component actions weren’t working properly. Turns out he had two actions defined that were supposed to happen in succession; however, the order that these events happen is actually indeterminate while the actions are executed in order, they are run asynchronously and can therefore finish out of order, but the interface itself makes it seem as though they will run sequentially. [image]