Pinned Persistent Subscription: order of events within one bucket

this line in you documentation caught my attention and I’m not quite sure how to interpret it:

Pinned: The main aim of this strategy is to decrease the likelihood of concurrency and ordering issues whilst maintaining load balancing. This is not a guarantee and the usual ordering and concurrency issues must be handled.

Does this mean that the order of messages within one Client is not guaranteed, or that the order within multiple Clients is not guaranteed?

Given one stream with the Id X and the Events A,B,C.

Am I guaranteed that the client which was assigned the stream X bucket will receive the Events A,B,C in order or not?

with a single subscriber you will receive the messages in order but retries etc can come out of order, if you are looking for assured ordering use a catchupsubscription