Your Setup:
- SeaTable web
Describe the Problem/Error/Question:
During the afternoon & evening of Feb 22, 2026 I inputted 3 different entries in my Base. During that time I successfully added some data in some of the cells in those rows as well. The Base was responding and accepting the data because I have cells change colour codes based on data being entered and all that was working; the cells changed from green to red etc as expected. The next day (today Feb 23) I went to that base; that tab was open in my browser, and successfully edited 3 of those rows again by adding yet more info into other cells. All seemed well. One of those cells was in a column that had a filter applied to hide the row if the cell was not empty; as soon as I put my entry in that cell ST then hid the row as per normal behaviour. Again all seemed well. About 2 hours later I went back to my web browser (Chrome) and it was not responding. I did I force quit and restarted it; it offered to reload my tabs, which I did. When I went to ST, all 3 of the rows of data that I had inputted and edited yesterday and this morning were… poof … gone! This is where it gets weird. I manually reconstructed the data (there goes 45 minutes of my life lol). As a test, I nervously navigated out of the Base and then reopened it to see if it saved my new inputs. And the original data which seemed lost, and the newly reconstructed data, was both there. I believe one edit had not been captured, but all 3 original rows were there. So of course I had to delete the duplicate entries. So I don’t know what the conclusion is. The data was there… then was not displayed for some reason after Chrome crashed, but then magically reappeared after I closed & reopened the Base. Obviously there is a technical explanation, but I think the issue is that ST is doing something weird with data input / saving / displaying because all my older data was there. So why would edits in the most recent 18 hours be displayed but then not display after the browser freezes and then reappear later? I think there must be a fault in how the Base is capturing and displaying data.
