No, but if your use case depends on the order in which things are processed, then you have ensure that the ordering you require is made to happen.
In a case like this, you could put timestamps on everything, and buffer (in Flink state) whichever side is ahead. As events arrive from the side that’s further behind, you can go ahead and process the older events from the side that is ahead (taking them from the buffer). (This is a somewhat simplified explanation — just trying to convey the flavor of what’s needed.)
Temporal joins (from the SQL/Table API) implement this pattern for you, so in most cases there’s no need to implement this logic yourself.