Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

queue - aborted no available instance

See original GitHub issue

[REQUIRED] Step 2: Describe your configuration

Extension name: firestore-send-email
Extension version: 0.1.10
Configuration values (redact info where appropriate):
- compliant

[REQUIRED] Step 3: Describe the problem

error

queue - aborted no available instance

Steps to reproduce:

Expected result

Actual result

Issue Analytics

State:
Created 2 years ago
Reactions:3
Comments:6 (2 by maintainers)

Top GitHub Comments

1reaction

waste-appcommented, Sep 3, 2021

@waste-app per the Cloud Functions docs, it looks like this may be caused by a Cloud Functions internal error. If you update to the latest version and are still experiencing this, please reach out to Firebase support.

response: …Now, issues or bugs in an existing extension are better attended on GitHub, for that you will need to create an issue in the Firebase Extensions GitHub. I know this is not the answer that you expected, but they are better prepared to help you with troubleshooting and also feature requests for existing extensions…

0reactions

i14hcommented, Dec 21, 2021

Thanks for the feedback everyone. Closing this as it’s more of a runtime platform issue and nothing needs to be changed in the extensions atm.

Top Results From Across the Web

Google Cloud Function The request was aborted because ...

The ongoing issue has an indirect effect where no instances can currently handle the request. There's an initial bursts of requests coming, to...

Troubleshooting Cloud Functions

Cloud Logging errors related to pending queue request aborts ... The request was aborted because there was no available instance.

[ Tracking Bug only ] GCP Serverless ( Cloud Functions ...

The request was aborted because there was no available instance. Mitigation / Troubleshooting. These errors can at times be attributed to customer's workload...

The request was aborted because there was no available ...

tl;dr GCF nodejs runtime used to silently drop requests when instance couldn't be scaled fast enough to respond to demand. Now it's logging...

"transfer aborted: instance not found" when trying to do ...

... and so far two of them have a high chance of getting “transfer aborted: instance not found” when accepting a dungeon queue....