Quickbase extremely slow and some features will not load at all
Quickbase currently very slow and some features of our app are not loading at all. I cant find a a place to report Quickbase issues so reaching out here. Quickbase status page only shows downgraded performance for Quickbase community which for me, seems to working perfectly, while Quickbase itself is not. Anyone else experience issues and know of a place to report these performance issues? Thanks for your help.
Try to understand how resources are shared
I know that when you use cross app relationships, resources are shared, where as if something is populated via Pipelines or a Sync table, they are not shared resources. However, a table to table import may share resources, and I believe even something like a report link will share resources. My question is this: Are the resources only momentarily shared (so for example when someone is looking at the report link, or the table to table import is running at that moment in time the resource is tied up), or is it more significant than that? I've had it explained to me that in a sense, my app is being run in one of QuickBases' 'lanes', but if I have cross app relationships, now all my apps 'travel together'. If I have a table to table import, or just a report link, have I now tied all those apps together as well? Does having a single report link do as much damage as a full cross app relationship? Same question for table to table import, etc... ------------------------------ Mike Tamoush ------------------------------
Record Creation Delayed
I have a URL which creates two related records, via an automation, and returns the user to a page. It definitely seems as if there is a small delay between clicking this button and when one of the records shows up in a report. For instance, if I click the button and land on the page, and then immediately click a link to go to a report the new record does not appear. But if I wait a moment it does appear. This is problematic. Any suggestions?
How many fields is considered *too many* (where it affects performance?)
How many fields is considered a lot of fields, where it might start affecting performance? Do data input fields effect performance, or only summary fields, and related fields? Most of my tables have 50 fields, 100, or a large one maybe 300-400. But I have one table that is approaching 800 fields and quite a few forms. It still works and performs great, but I wonder if I am getting too large, or if people will say, 800? I have 2000 fields! ------------------------------ Mike Tamoush ------------------------------Slow form load for some users?
Hello, A few of my users have reported very slow form loading, specifically in edit mode. When I try to recreate the issue by impersonating the affected persons, I'm unable to do so, i.e. the form loads as I would expect. Other than the potential for slow internet speeds on their end, any idea what may be causing the problem or how best to troubleshoot? Thanks, Patrick ------------------------------ Patrick Dunn ------------------------------Re-asking this Database Lock issue question
This seems to be a database lock issue and I have asked a few days ago and no one has provided a real solution (only temporally fixes). We created a form using for staff to register for daily available slots. Unfortunately, when we tested the form, we did not test it for concurrent data entry. And lo and behold, when we opened the registration for the event, we found out that when two users were working on the form at the same time, the form rules could not stop them from passing the limit (e.g., if one slot was available two people could sign up for it, provided that when they opened the form to register, one slot was available). Is there a way to fix this so that two people cannot register for the same slot?
Best practices - combining two apps to one
Looking for advice on best practices. I currently have two related apps that, as they've evolved, I am thinking would make much more sense to be in one app... for better user experience, easier/cleaner reporting, and easier/cleaner API calls from/to external systems. My concern with doing this is the number of fields already on each table. By combining the tables in these apps, I would end up with over 750 fields on one table... should I be concerned with performance issues if I do this? We use these applications to drive our daily production operations so performance issues would be a huge concern. ------------------------------ Jennifer Miller ------------------------------QuickBase 'double loading' on Firefox
Has anyone else notice the behavior recently change on Microsoft firefox? Not sure if it is due to a recent update in QB or Firefox (this does not happen in Chrome), but curious if anyone else has suddenly experienced all QB pages 'double loading.' That is to say you click on a table, or record, or any page in quickbase, it begins to load and then immediately begins to load again. I started noticing this maybe a week ago. Curious if anyone has the same behavior and knows the cause. Definitely browser specific, so I can simply change browsers if needed, but wondering if anyone else has insight. ------------------------------ Mike Tamoush ------------------------------
502 Errors this morning
Multiple users of my quickbase apps are reporting connection issues and extremely slow page loads intermittently this morning. Is anyone else experiencing the same issue? I have confirmed with my company the issue is not related to our server or VPN. ------------------------------ Paul Peterson ------------------------------
