Considering the behavior we are observing, and I dealt with the same thing in another complicated workflow I was trying to set up with a lot of rules working together, Iām fairly confident that when a rule run begins, thereās a data object in the code that tracks the entire sequence of all the rule runs and all the actions associated with that series of triggers and actions, even if it stretches across rules ā letās call it a āRule Run Batchā. I donāt see any evidence of it in the API, but it makes sense that there would be something like a āRule Run Batchā with an associated gid. And every rule can only run once per rule run batch. Then hypothetically if the first rule in a series of five chained rules is triggered again by a rule run batch with a gid that it has already seen, it wonāt run again.
This came after experimenting using a sequence of 5 sequential rules that all triggered each other and the 5th went back and re triggered the first rule which then did not run again.
Just a hypothesis, but Iām guessing thatās how itās all structured.