Triggers firing too quickly in sequence

(Andrew Harris) #1

Matrix Version: v5.4.1.3

Wanted to create a trigger which would morph a user from Backend User to Simple Edit User.

Trigger fires fine, with two actions: 1) Morph Backend User to User, and 2) Morph User to Simple Edit User. Then stuff gets weird!

The morphing gets done, but it seems like the second action is fired before the first is complete - system throws a quite astonishing, and hitherto unknown error. I definitely need to put some space between those actions, or split them into two separate triggers (which is just messy, and I didn’t want to do it!)

Any helpful suggestions?

(Bart Banda) #2

That has been fixed in 5.4.2.2 with the simplified morphing where you don’t need to go via a specific path: https://matrix.squiz.net/releases/5.4/5.4.2.2#simplified-asset-morphing

I’d say other than upgrading, I think having 2 triggers would be the way to go… :frowning: