@karimoo I believe the issues here are most commonly caused by using data that’s not yet available.
For example if you have a home screen with a filtered list, and the filter includes something from Logged In User > name, then we’ll have to load the logged in user first, then load the filtered list, based on the response that included the logged in user’s name.
Right now, we’re requesting all the data at the same time, so Logged In User is not available by the time we try to load data from Airtable.
We are working to solve this issue, but unfortunately it’s a bit involved, and may take a couple of weeks still before it’s fixed.