I’m using the Softr map block, which pulls data directly from Airtable. However, I’ve noticed that the map takes a few seconds to render when the page loads. It appears the delay is happening during the data fetch and rendering process, as the map doesn’t appear immediately.
Thank you for the kind words and for taking the time to check out the app!
You’re absolutely right—the map does include a large volume of data points, and the delay is something I’ve noticed as well. I appreciate the insight regarding Airtable’s API limits; that definitely helps clarify the bottleneck.
I’m currently exploring alternate data sources that might handle higher volumes more efficiently. If you have any specific recommendations that work well with Softr, I’d love to hear them.
Thanks again for the support and feedback—really appreciated!
I would look at using an SQL data source for this (Supabase, Xano, etc.) Note, you can use this data source for just this block to improve its performance. Hope this helps!
I’ve identified the root cause: the map is loading only after all user profile data is retrieved from Airtable. There are around 1,800 profiles, which results in 18 API calls (100 records per call) before the map API is even triggered.
Even though I’m not referencing any user profile data on the homepage, it seems Softr is still attempting to load all of it during page render.
Could you help me adjust the sequence of these API calls so the map can load independently and more efficiently?
I am having the same issue, but loading a few hundred items from Notion. Not a developer myself, my contracted developer was adamant that it should be easy for the Softr team to fix their backend to fix your problem, and mine.
He suggests that Notion’s limitations are not the bottleneck, Softr is, because it can be fixed on their side. @Jjenglert even @PavanRaj s 1800 pins is a tiny bit of data?
Hi Customer Support,
I am experiencing unacceptable latency and fall-out issues in my. App. A few technical questions in order for my team to understand the root cause. We use Notion as database.
Is Softr able to render all 4 blocks on the same page from one API call, or does ot make one API call for each block/seperate calls. I need to understand this to make Notion API call limits.
I experience errors in the app where content even from a single-block page does not load, sometimes in the beginning of login. It may then load after a reload of page, and drop back off after a few seconds. So I need to understand if your backend uses Retry with backoff, and why the enabled cache in your backend does not protect the UI.
Are Notion side API calls pr logged in users? Ie will the issue accelerate with multiple users on the platform at the same time?
Please, can I get a technical response to this request, as I need to contain this issue to understand if Softr is able to support our frontend needs.
We have considered migrating to Supabase to expand api-call rates, however I would need to fully understand the above questions, as our developer does not see that the Notion API limit is a logical root cause of the Softr issues we are experiencing.