I need a firebase cloud function to trigger every 20 seconds.

[RobG]

I need a firebase cloud function to trigger every 20 seconds, but since the cloud scheduler has a ground limit of "every 1 minutes" frequency I can't do that, what is the best way to solve this?

[Michael Bleigh]

The simplest way to do this would be to use timeouts to control your execution so that it executes three times within a loop:

function sleep(duration) { return new Promise(resolve => setTimeout(duration, resolve)); }

// in your scheduled function that runs every minute

const promises = [];

promises.push(doThing());

await sleep(20000);

promises.push(doThing());

await sleep(20000);

promises.push(doThing());

await Promise.all(promises);

The downside to this is that you will be charged for the execution time while waiting, so you will be guaranteed to be charged for 40s of execution time every minute. There is not a simple answer outside of this, though -- schedules can only execute at fastest one minute so you would need to set up a different way to trigger an event (i.e. a VM that dumps a message into PubSub every 20s) to achieve it other ways.

On Sun, Jul 26, 2020 at 8:33 AM RobG <robg...@gmail.com> wrote:

I need a firebase cloud function to trigger every 20 seconds, but since the cloud scheduler has a ground limit of "every 1 minutes" frequency I can't do that, what is the best way to solve this?

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/0dd076f3-1432-4c87-8c41-36a114d95181o%40googlegroups.com.

[Tim Schönborn]

In case anyone finds this and then wonders why the function doesn't sleep:

There's a typo in the first line, it should be setTimeout(resolve, duration) (instead of (duration, resolve)).

[Kato Richardson]

How unfortunate. Additionally, the linter can't catch this since both are integers. So annoying. Yet another case for State patterns vs argument lists. 

Good eye on spotting a solution!

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/79e99bfd-5383-443c-8f15-722f721a8a19n%40googlegroups.com.

--

Kato Richardson |

Developer Programs Eng |

kato...@google.com |

775-235-8398