@ThinhDinh apologies for the lack of clarity here, but confirming I have done this + this is not an isolated issue. It has been reported to me from different users. After I checked, I get the same results.
hello! Can someone please take a look at this? I have tried to troubleshoot myself, but still encountering several issues reported from different users.
In my experience that usually means you have some columns set up in a way that causes all rows in one or more tables to run all of there calculations all at once. Do you have any relation or query columns that rely on computed columns? Do you use a lot of query columns? Do you have a lot of computed columns or a lot of complex logic? If you have large tables and something causes all computed columns to calculate at the same time, then it can take a while for the tables to process when accessed after the app loads.
Yes, I do have some relations that rely on computed columns. E.g., a statistics table that captures all reservations from a computed column (date is formatted differently). That being said, the amount of data in this app is fairly low in my opinion (including the computed columns), so not really sure why this is happening