# Firebase - Values updated automatically reverted **URL:** \ **Category:** Questions about Thunkable X\ **Tags:** firebase\ **Created:** [May 4, 2019, 1:17pm UTC](https://community.thunkable.com/t/firebase-values-updated-automatically-reverted/75802 "2019-05-04T13:17:56Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![actech](https://avatars.discourse-cdn.com/v4/letter/a/3d9bf3/32.png) [@actech](https://community.thunkable.com/u/actech)\ **Post date:** [May 4, 2019, 6:48pm UTC](https://community.thunkable.com/t/firebase-values-updated-automatically-reverted/75802/7 "2019-05-04T18:48:41Z")
Unfortunately, I do not have a ready-made example yet, but Mark showed an example of working with an asynchronous block. > [@Asynchronous Blocks within Loops](http://community.thunkable.com/t/asynchronous-blocks-within-loops/33524): > > We recently had a bug reported by a user who was seeing strange behaviors within the “then do” part of a RealtimeDB.Save block which was within a loop block. The strange part was that even though each execution of the RealtimeDB.Save block was called with the current value of the loop variable (or something based on the current value) the blocks within the “then do” part always just saw the last value of the loop variable! This is a well known issue when using asynchronous function blocks (lik… I do not know your final task, but I would consider the option when we first prepare all the data to write to FireBase, and then save it with just one call to the Save method. --- _[View the full topic](https://community.thunkable.com/t/firebase-values-updated-automatically-reverted/75802)._