Set timeout for Cloud Functions for Firebase does not persist in the Console; is this a bug?

Lindauson picture Lindauson · Apr 11, 2017 · Viewed 15.3k times · Source

Update: I updated the question, to reflect what I described in the body of the question, and what was happening at the time. It also justifies why I did not mark Sanyam's response as correct. There was a bug in the Console that was causing the timeout values to be ephemeral. @MichaelBleigh's response was the most pertinent, letting me know when the issue was resolved.

I have a Cloud Function that needs to run past the default 60 second timeout in some edge-cases.

The issue is, while this value can be changed in the Cloud Functions section of the Google Cloud Developer Console, it reverts to the original default after each deploy.

Is there a way I can persist the changes to this setting, perhaps in one of the Firebase configuration files?

Answer

Sanyam Jain picture Sanyam Jain · May 11, 2017

Default timeout can be changed here https://console.cloud.google.com/functions/list
select function >test function > edit > timeout