Functions emulator does not honor timeoutSeconds
See original GitHub issue[REQUIRED] Environment info
firebase-tools: 8.16.2
Platform: macOS 10.15.7
[REQUIRED] Test case
exports.zip = functions
.runWith({ memory: '1GB', timeoutSeconds: 540 })
.https
.onRequest(zip);
[REQUIRED] Steps to reproduce
Run function on emulator such that it takes a long time to execute.
[REQUIRED] Expected behavior
I expect that the function times out in 540 seconds.
[REQUIRED] Actual behavior
The function times out in about 60 seconds (I did not time it, that is a guess).
Is it a known issue that the emulator doesn’t respect timeoutSeconds
, or did I do it wrong?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:9
- Comments:28 (9 by maintainers)
Top Results From Across the Web
How to configure timeout of Firebase functions on local
The timeout set in this new .env.local file should be honored. ... the Firebase emulator ignoring runWith({timeoutSeconds: }) when running ...
Read more >Connect your app to the Cloud Functions Emulator - Firebase
A demo Firebase project has no real Firebase configuration and no live ... However, the emulator does support timing out functions via the...
Read more >Firebase functions emulator runtime options - Google Groups
The answer to your question is no - local emulator will not enforce memory limit on emulated functions. As implemented, the emulator simply ......
Read more >Oracle® Hospitality Simphony
With this release, Simphony no longer supports the DT. Research 430 and Motorola 55A handheld devices. MICROS Handhelds functions are.
Read more >Ivanti Connect Secure Administration Guide - Product Documentation
Clients that use Network Communications Protocol (NCP) do not honor policy ... In a federated network, the IF-MAP server functions as the repository, ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah, it’s an undocumented breaking change on v10.2.0
Looks like setting env
FUNCTIONS_EMULATOR_TIMEOUT_SECONDS=540s
is a workaround for the dropped featureIt can be added on a .env.local file on the functions folder to be used only on emulator
Firebase CLI v11.4.0 should now support timeout on your function configuration - no need to setup
FUNCTIONS_EMULATOR_TIMEOUT_SECONDS
environment variable.