Cloud Run Function Unavailable Errors

[rxnvpr]

Hi all,

I’m building a serverless application using Google Cloud Run, where several Cloud Run services (functions) need to interact with each other. I’m using Cloud Tasks to queue and trigger these services in a controlled sequence, and also to track success/failure at each sub-stage.

It works well about 50–60% of the time, but for the remaining executions, I’m seeing “unavailable”errors in the logs. I’m struggling to figure out what’s causing this — there are no obvious patterns in timing, payload size, or concurrency that I can see.

Has anyone experienced something similar or have thoughts on what could cause intermittent unavailability of Cloud Run services triggered by Cloud Tasks?

Appreciate any and all leads  🙂

Thanks! Target Cloud Function is Unavailable

[Joy_S]

Hi @rxnvpr,

Welcome to Google Cloud Community!

"Unavailable" errors in Cloud Run logs can stem from several issues. Here are some potential causes and how to resolve them:

• Cloud Logging Integration Issues -  Errors may arise when writing to Cloud Logging, possibly due to misconfiguration. The error message might read: "Failed to send to Cloud Logging. Status: UNAVAILABLE: Server is not responding". Check your Cloud Logging integration to ensure nothing is missing from your configuration.
• Client-Side Errors -  Symptoms: Your application receives repeated errors when making requests, such as DEADLINE_EXCEEDED or PERMISSION_DENIED. With custom client libraries or altered retry settings, you might encounter UNAVAILABLE or UNREACHABLE errors. Infrequent errors are normal in distributed systems. Focus on a high number or percentage of failures over at least five minutes before investigating. If the UNAVAILABLE error detail is "502: Bad Gateway", it indicates network connectivity problems, not a Pub/Sub issue.
• Resource Limits - Container instances exceeding memory limits can lead to HTTP 500 or 503 errors. Requests often fail with a 500 error when the container crashes due to being out of memory (OOM). Check Cloud Logging for OOM errors

You may check this documentation for more information on known issues in Cloud run.

If the workaround above doesn't work, you can contact Google Cloud Support for a more in-depth analysis. When contacting them, please provide comprehensive details and include screenshots. This will help them better understand and address your issue.

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.

[rxnvpr]

Thank you so much for your reply @Joy_S . Unfortunately, it's none of these. The error I get is "NOT FOUND" as you can see here.