ArticlesBlog Understanding Cloud Functions: Dealing with parallel execution (Firecasts) August 29, 201910 No related posts. Related tags : android apps app developers app development app memory Cloud Firestore cloud functions cloud functions for firebase cloud functions tutorial concurrency Firebase firebase 2019 Firebase Developers firebase function instances firebase instances firebase updates function instances IOS apps mobile app developers multiple instances firebase node.js running parallel instances stateless functions Post navigation Previous Article Magento 2 Multi Vendor Marketplace Store Pickup Add-On Next Article Dealing With Ostomy Blockages: Ostomy Tips Comments (10) February 21, 2019 at 12:40 am alpha Reply February 21, 2019 at 12:48 am goodness gracious! Reply February 21, 2019 at 1:00 am Thanks, Doug 🙂 Reply February 21, 2019 at 3:55 am Doug, do you approve the idea of creating a database collection of jobs queued which are polled, possibly retried and marked as failed or succeeded?This could solve the delete before create job order problem and be useful for recovery yet it adds complexity Reply February 21, 2019 at 1:43 pm I have one function which only runs onCreate. I have created a document which triggers that function, and it triggersed 3 times in a matter of milliseconds ( by looking at the logs ) … even through that document has only been created once. No other documents were created that could trigger it or anything, I was just testing my app, topped up 50$, created the credit document, and function triggered 3 times, my wallet ending up with $150. Quite weird behavior. The stripe example offered in the github repo doens't really help .. as that idempotency key is something they support, and not firestore. I really can't think of any workaround .. if you guys have any idea .. please advise Like always, good work with the videos! Reply February 21, 2019 at 3:51 pm "System may deliver same event more than once, this is rare". Rare, I thought this a norm. This happens frequently in my case, noticed this only during testing ( trigger & monitor logs for console.log ). In my function if it does the same thing, there is no problem, it will try to update same data. I think in firebase when you try to update same data, I think it won't update it, I guess as most databases. So basically if it functionally works, I stop monitoring logs, never had to worry about this. Had to worry only if I am counting invocations, but I am not doing that. Reply February 21, 2019 at 7:03 pm Hey Doug, nice video. I hope a video on Dataflow with Firestore for aggregating data 🙂 Reply February 22, 2019 at 4:36 am Love this series! Reply February 22, 2019 at 7:56 am Thanks Doug and the Firebase teams, I'm loving this series on Cloud Functions – totally relevant for me as I advance my development into those features. Reply February 22, 2019 at 5:07 pm Can I make an api using cloud functions? Reply Comment here Cancel reply Comment Name * Email * Save my name, email, and website in this browser for the next time I comment.