are messages guaranteed to be enqueued in order?

[shuttlefan]

I'm logging to help debug.
On the block diagram, I've got one log point outside the MHL case and one inside.

Most of status does follow the order shown.  However, every so often, it gets flipped. 

The status from inside MHL case comes before the outside as shown below.  This happens through out.

1/30/2025 1:50:48 PM; ADSSClientQ 0; keepAlive
1/30/2025 1:50:48 PM; ADSSClientQ 0; KeepAlive MHL 296
1/30/2025 1:50:48 PM; ADSSClientQ 0; getEventCondLastUpdateTime
1/30/2025 1:50:55 PM; ADSSClientQ 0; keepAlive
1/30/2025 1:50:55 PM; ADSSClientQ 0; KeepAlive MHL 297
1/30/2025 1:50:55 PM; ADSSClientQ 0; getEventCondLastUpdateTime
1/30/2025 1:51:02 PM; ADSSClientQ 0; KeepAlive MHL 298
1/30/2025 1:51:02 PM; ADSSClientQ 0; keepAlive
1/30/2025 1:51:02 PM; ADSSClientQ 0; getEventCondLastUpdateTime

is there not a guarantee on messages being queued in order thy are sent?
Sign of something wrong with the queue?

[ChrisFarmerWIS · Accepted solution]

Try changing the error wire like this:

[shuttlefan]

---

@ChrisFarmerWIS wrote:

Try changing the error wire like this:

---

Right, I will do that.  
I just thought there is no way that the outer message would be slower than then stuff inside that has more steps to do.

[joerg.hampel]

---

@shuttlefan wrote:
I just thought there is no way that the outer message would be slower than then stuff inside that has more steps to do.

---

It is the *exact* opposite, actually. There is absolutely no way of telling which of the parallel pieces of code will execute first. Good catch, Chris!