I'm not sure if this is a bug or if I'm not understanding how order of operations are supposed to work in different cases.

I've created a sample Max for Live patch to demonstrate the issue.

In version 1, which is triggered manually, I get the results I expect.

In version 2, which is triggered when Live transport reports beat 1, I do not get the results I'm expecting.

Why don't the two versions produce the same console results?

If it were just an issue of only the console not correctly printing operations in order that would be fine, but the console reflects what is actually happening and is causing major problems in a much bigger patch I'm working on.

I've created a sample Max for Live patch to demonstrate the issue. 

In version 2, which is triggered when Live transport reports beat 1, I do not get the results I'm expecting. 

max-for-live-order-of-operations-not-working-as-expected

Max handles manual triggers differently from time-based triggers, as explained in this article

https://cycling74.com/articles/event-priority-in-max-scheduler-vs-queue

So inserting [deferlow] on your plugsync~ output should give the same behaviour as manual trigger.

Max for Live Order of Operations Not Working As Expected