_ah/healthcheck errors pinging v1 onRequest functions incessantly on deployment at random

[rob-yeshearing]

Related issues
No related issues found, but this pertains to the _ah/healthcheck error that occurs when deploying Firebase V1 onRequest functions.

[REQUIRED] Version info
node:
18.0.0

firebase-functions:
5.0.1

firebase-tools:
13.13.3

firebase-admin:
12.1.1

[REQUIRED] Test case
exports.testFunction = functions.https.onRequest((req, res) => {
res.status(200).send('Test function');
});

[REQUIRED] Steps to reproduce
Create a basic Firebase onRequest function as shown above.
Deploy the function using firebase deploy --only functions.
Check the logs for any _ah/healthcheck errors in the Firebase Console or Google Cloud Logs.

[REQUIRED] Expected behavior
The function should deploy without triggering health check errors, and the endpoint should be accessible without issues.

[REQUIRED] Actual behavior
After deploying the Firebase V1 onRequest functions, the following health check error appears in the logs:
https://2-dot-[your-project-id].appspot.com/_ah/healthcheck
The request was aborted because there was no available instance.
No additional traffic or activity seems to trigger the creation of new instances, and this log entry is repeated over time.

This happens at random with all onRequest v1 functions.... unsure of why or how to stifle these errors upon deployment. I can't upgrade to v2 due to clients using the v1 endpoint.

Were you able to successfully deploy your functions?
Yes, the functions are deployed, but the _ah/healthcheck error persists in the logs.

[CorieW]

Hi @rob-yeshearing

Thanks for reporting this issue! We’ve received it and are reviewing it. We’ll provide updates as soon as possible.

[CorieW]

I'm unable to reproduce this issue with the latest versions of things. I've deployed 10 times and haven't seen this problem occur. Do you still experience this issue?

[google-oss-bot]

Hey @rob-yeshearing. We need more information to resolve this issue but there hasn't been an update in 7 weekdays. I'm marking the issue as stale and if there are no new updates in the next 3 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@rob-yeshearing if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.