When you add an additional action to a single action trigger, the first action remains immovable (i.e., it cannot be reordered across other actions). To overcome this, I've gotten into the habbit of making the first action Null so that I have flexibility with the trigger - not only at the moment I create it, but in the future as well. Otherwise, in situations where I am revising major functionality in my setup (editing a lot of multi-action triggers) it adds a lot of time to configuring things if the first action cannot be easily moved around as I test WIP triggers.
One of the downsides to this is that it becomes much harder to visually distinguish and identify triggers since the first action is null. While only the full action set can tell the full story, it helps to be able to see the first action as it often can be enough to describe what the trigger is about. I do already make heavy use of the Notes section to aid in this manner, but when dealing with hundreds of triggers every bit of visual information helps to make sense of things.
Somewhat related to this is that I call triggers using UUIDs a lot, which means I always preserve my triggers instead of creating new ones (otherwise a new UUID would be created). This is relevant in cases where Copy / Pasting triggers would be the most efficient way to copy things, yet the first action cannot be copied alongside the others.
I did find and older thread from over 2 years ago talking about the same thing, but without the solution I am proposing - which I think is much more desirable and easier to implement. Thus I decided to create a new thread. Hope that's OK.
Thank you.
. Sorry to keep you so busy Andreas! But also, be aware that there's more threads incoming!! 