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.
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.