I have a cloud run endpoint that gets triggered by a push type pubsub subscription and the cloudrun api is a composite api which does 2-3 operations and then it returns. I am observing at high load times few of the third party things like redis and firestore produce timeouts. In that case I am expecting pubsub will control the load (as per the document -> delivery rate) since there will be nacks coming from service. All the requests are getting successful in push backoffs but my service is experiencing the failures. Please help me what i am missing or how to monitor the push window?

In gen1 Cloud Function with PubSub trigger, the subscription can easily be edited using the CLI, because the subscription name has a deterministic name of the pattern “gcf-<FUNCTION_NAME>–<TOPIC_NAME>”. This is very useful for subscription settings such as retry delay, ack deadine, and message retention duration.

I have a GCP Workflow in which I need to publish a pub/sub message that contains data AND some attributes. These are three steps that initialize some parameters, create a map for the attributes, then publish the message: