This message was deleted.

It sounds like you are using an exclusive subscription type on each function instance, which results in duplicate processing, etc. Can you tell us what the desired consumption pattern is? For instance, would you want each message in the topic processed exactly once by just one of the function instances, like a work queue?

Yeah, I think queue like behavior is the kind of the behavior that we want unfortunately, it's shared across multiple teams and so we can't just make it exclusive. I'd like our services to behave more like a queue but we can't turn it into a queue because other teams need to be able to access it like a topic. It works great when we have the single pod but when we attempt to scale then we have 2 identical services subscribing and in that case the ability to group our round robin between them would be great

What you want is the shared subscription type. Using the same subscription name across the function instances will give you the behavior you are looking for.

Thanks so much. I must have misread that and thought it applied to the whole topic. I figured what I was looking for existed but was just missing something. I had thought about the subscription name but we had run into an error when names were identical but to your point we are probably in exclusive mode which makes a lot more sense now.