It seems like you are dealing with message flow control issue [1], where the subscriber client might be slower in processing and acknowledging messages than Cloud Pub/Sub is in sending them. In your case, this might have led to a backlog of messages to one client because it doesn’t have the capacity to handle the influx of messages, thereby, being unable to send its messages quickly enough to the second client it gets stuck.
To resolve this, I suggest that you use the flow control feature of the subscriber to control the rate at which it receives messages. Follow the example provided in this documentation to try out the flow control feature [1]. You can also reference this troubleshooting guide for future reference [2][3]. Hope that helps. Let me know how that works for you.
[1] https://cloud.google.com/pubsub/docs/pull#message-flow-control
[2] https://cloud.google.com/pubsub/docs/troubleshooting#create
[3] https://cloud.google.com/pubsub/docs/push#app-engine-standard-endpoints