My app exceeded its row limit by 300 records (out of 25k), and I got a bunch of emails from users this morning about this pop-up.
Can we please disable this in the live apps? I didn’t even get notified about exceeding row limits.
The Continue button feels new to me. Before I think you were completely locked out if you exceeded limits. At least the Continue allows you to access the app. But isn’t that the point of the warning to you and to your users…that things may not work as expected due to exceeding row limits?
I don’t know why you didn’t get a warning, unless your rows increased rapidly in the last day or two.
Wouldn’t the solution be to reduce your row usage? Then the warning should go away.
In the past, we got a bit of room. I do remove rows - I don’t think it suddenly exceeded my limits.
I think there shiuld be a label in the glide app with a warning. I was building in it all day yesterday.
I think either way - it should be optional having this pop-up. It kind of makes you app look cheap if random Glide popups happen in your published app.
4 Likes
So what should happen if limits are exceeded and there was no popup? Would it become disabled in some other way? Get an email with a few days warning before lockdown? Get billed for overage? Genuinely curious what your thoughts are, because I imagine there would have to be some sort of consequence, but I don’t know what that would be.
- I would pay for row overage for sure. If it worked similar to how updates work, I would definitely pay extra if it keeps the app going. It doesn’t seem to be an option though.
- I think if there was a label in the Glide app saying “You are about to exceed your row limit and your users won’t be able to do X” when limits are approached that would be good.
- Definitely yes to emails.
- I wouldn’t want the pop-up in the app under any circumstance. I rather the app just not work rather than a pop-up being displayed saying “This app has reached its row limit”
- I don’t mind if a popup like this comes up in Glide but definitely not in the live app, especially when you are on paid plans.
2 Likes
We send you quota emails as you approach 25k.
Apps with over 25k rows are not supported unless using a queryable data source.
1 Like
I agree with you, Connor.
First and foremost, I think the app owner (the account that made the app) needs to be warned by whatever channel is deemed appropriate: in the dashboard, in the builder of that app, via email. These 3 seem the minimum.
Second, I think it’s fine if the users of the app are forewarned that the app might not function properly, but I do find the wording could be changed to something like “For technical reasons, this app might not function as expected. Please contact the app owner […]” or something like that. Referring to row limits is technical (jargon-y) and probably not the way a user would see things. It would be unsettling at best.
David mentions that you, the app owner, received an email. As it should be. This email, however, does not justify or compensate for a poorly worded warning message inside the app.
What do you think the dialog should say?
You are going over a hard technical limit of your app. We cannot allow apps to run past this limit or your app will break and it’s a nightmare for us to support customers whose apps are broken. We have to put a hard block in place when you exceed what Glide can handle.
For technical reasons, this application might not function as expected.
Please contact the app owner to resolve this issue.
There are millions of Glide apps. If we don’t mention “row limit”, we’ll have 100 support request per day from Free users alone asking what’s wrong.
I don’t see how row limits is of any interest to app users. Limits concern the app maker. And one is not necessarily equal to the other. Irrespective of the plan.
But I see what you mean. You are assuming that the users of apps on the Free plan are the same as the maker. Possibly and even probably. But this assumption is probably false on paid plans.
Two messages for two personas:
On all plans, dialog inside the app in production:
For technical reasons, this application might not function as expected.
Please contact the administrator of the application to resolve this issue.
On all plans, via email, in the dashboard, and in the builder:
This application has reach its row limit.
Resolve this issue by reducing the data inside the app or upgrading plans.
1 Like
Our problem is that developers ignore our emails. If we don’t put an impediment in the app, with enough info for the developer, it’s impossible to communicate.
1 Like
I agree with this.
What the app developer (me) and the app user see should be different.
Even something as simple as: “We are experiencing technical difficulties, and the app might not work as expected” is more than sufficient.
The end user doesn’t need to know what the issue is. It could be row limits, updates, not paying your bills etc. - ultimately there is nothing the end user can do about it.
When I am in the app, the issue should be more detailed. It just makes for different user experience.
1 Like
From a product perspective, I think what I suggested above is good and should cover your bases:
- App owner to be warned in the dashboard, in the builder, via email.
- Users are also warned.
- Two different messages for the two different personas (app owner vs users).
1 Like
Is this really the best we can do? It just makes the app look cheap. I have no problem with the pop-up in Glide, but in the live production app as a massive overlay?
Also I didn’t receive an email.
@Connor_Finlayson Glide does not support over 25k Airtable rows in your app, period. Should we completely block access instead of this popup?
Yeah, that’s not the issue. I am aware of that and it is completely fine.
It is the massive pop-up in the live app that’s the issue.
I am not arguing for more than 25k records. I am saying put that notification in the Glide App Builder or at least put something more subtle in the production app like “this app is currently experiencing technical difficulties”.
Yes, we should let you customize any text in the app.
Or maybe show some sort of error when attempting to add a row after all rows have been exhausted. App should still run fully at 25k with no alerts to the end user unless they try to add a row and now cant.
The app is OVER 25k rows.
1 Like