Hello. I have a Trigger that listens for a specific metadata field being updated. When the Trigger fires, a Trigger Action updates the value of a different metadata field. However, the Trigger appears to be firing regardless of which metadata field is updated. The Action then in turn causes the Trigger to re-fire, resulting in a loop that only stops when Matrix runs out of memory.
Looking at the system log, there are alternating entries for fields 183343 and 181669 being updated, although no message to say that the Trigger has successfully fired.
Here's a screenshot of the Trigger setup:
Note that the Action shown in the screenshot is the only Action in this Trigger. Also, the Trigger here is limited to a specific asset for testing purposes, but will ultimately be applied to a folder of assets. The third Condition is where I was planning to increment a value so as to stop the Trigger re-firing after a certain number of times. However, I think this whole thing may be caused by a bug.
Does anyone know whether this is indeed a bug, or if I'm missing something and should be suitably embarrassed?
Any help greatly appreciated!