# Ocassional problem: changes in row(s) not saved

**URL:** https://community.baserow.io/t/ocassional-problem-changes-in-row-s-not-saved/4465
**Category:** Technical Help
**Created:** [February 8, 2024, 6:19pm UTC](https://community.baserow.io/t/ocassional-problem-changes-in-row-s-not-saved/4465 "2024-02-08T18:19:56Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![marcus](https://community.baserow.io/user_avatar/community.baserow.io/marcus/32/1289_2.png) [@marcus](https://community.baserow.io/u/marcus)
#### Post date: [February 16, 2024, 4:31pm UTC](https://community.baserow.io/t/ocassional-problem-changes-in-row-s-not-saved/4465/5 "2024-02-16T16:31:46Z")

</div>

hi @davide @olgatrykush  
It happened again today - a problem with data not writing into cells. A member who was working with baserow, was connected on the same (local) network as usual and there is no evidence that his/her computer could be not connected (logged in) properly to baserow.

Together with it also “Table not found” error occured, I mean database did not respond properly, like there would be no such a table.

I described it here:

> [@Was working fine then randomly, "Network Error"](https://community.baserow.io/t/was-working-fine-then-randomly-network-error/4304/7):
>
> Hmmmm. After five days, it happened again. This is not good frowning@bram what do you think - by what it’s caused? [obrazek] [obrazek] [obrazek] I think I have to restart my baserow docker container again. Again, after 5 days of running. This should’t be a problem of insufficient resources. My NAS has 32 GB of RAM and there is also SSD NVMe read/write cache and container’s resources are displayed like this: My NAS resources: [obrazek] My baserow instance is running only …

Also I downloaded the log from my baserow docker container immediately after it happened. How can I provide it to you (it has some 16 MB - csv or html format).

Any help with this will be very welcomed.

---

_[View the full topic](https://community.baserow.io/t/ocassional-problem-changes-in-row-s-not-saved/4465)._