I've recently been experiencing what are called "app load timeouts", where I will open one of my apps and rather than loading (even if it takes a few seconds), I instead get an error message or something like, "App waiting to load." In order to actually get the app to load, I need to either refresh my page or click on the app title link in the top-left. Although the page never loads if I simply wait, it will load immediately when I prompt a refresh.
I inquired with Customer Support and they explained that this is something new, implemented on the back end to improve overall performance with the site. While I'm all for performance improvements, this idea that I now have to load my apps twice every single time I want to access them seems like a pretty big step backwards from a user interaction standpoint.
It was also pointed out to me, and I have heard various discussions about this over the past year or two, that I need to "optimize" my apps. However it doesn't seem like Quickbase has a clear standard in terms of what "optimized" consists of, in the sense of, "if your app meets these standards, it will not timeout upon load." I find it a bit frustrating to say, "Hey, my app isn't behaving as expected," and be provided some vague advice that is more riddle than answer. And while I fully understand that everyone's apps are different and optimization can mean a lot of things, I would hope that there is some guidance to troubleshoot their own design decisions.
The one piece of concrete advice that I received was to create a pipeline that performs a simple API request that runs every 20 minutes, which I guess prevents your app from "going to sleep." But I fail to see how that could be considered anything other than a clumsy band-aid to a step backward in user experience.
Anyway, this is a bit of a rant, but I'm wondering how many other people have encountered this and what you're doing to remedy it. I have apps where this is occurring, and when I run the performance management tools, it just says that my tables have too many default fields, or that some tables don't contain any relationships, which can't possibly be driving app load issues, right? None of the performance insights are related to actual performance.
