Flow does not proceed to next weighted node in chain of events

[SyzygyBlue]

Recently updated node-red and actionflows on a new server with the same code. Actionflows of the same name do not flow to the next node of higher priority dependably, and instead just stops the flow at the first node of a singular name(.1) instead of flowing to name(.2) of a higher priority like it used to. This renders actionflows somewhat useless as they are unreliable in building a chain of actions.

In this scenario, EnqueueRecord.PFQ would fire, but the following one, EnqueueRecord.PFT does not fire and there are no errors, no warning, and nothing in the logs. It just doesn't execute the follow-on code. This is completely different from actionflows behavior that is documented, and I have personally observed for more than 5 years.

Node-Red v3.0.2
latest version of actionflows

[Steveorevo]

Can you post a minimal flow that reproduces this issue? Preferably with just actionflows, the standard palette and no other dependencies.