You have users that really pour themselves into the community and have a passion for Google Appsheet.
Please interact a bit more with your community what is going on behind the scenes and also address the concerns raised of recent.
This platform has so much potential that needs to become kinetic, please apply some pressure on those in charge of this platform on behalf of the community.
Quite right. They look like a bear in hibernation. ….. Leaving the community unattended and leave the users alone.
I can only speak for myself, but I have been trying to make a routine of checking the community more often recently and answering questions when I can. I don’t always have context on the problems people encounter though. Is there a particular issue or concern you had in mind?
Hi @Adam-google ,
thank you for your response. @Denzil_Snyman wrote exactly what I was planning to say.
There’s a critical production issue that multiple App Creators are reporting in this thread:
I mentioned 5 Google staff members 9 days ago, but there has been zero response from any of them.
It’s now been 12 days since the issue was first detected, and not only is it unresolved, but the complete silence from staff leaves us with no visibility into the current status or any remediation efforts.
AppSheet Support continues to be unhelpful as usual.
Given that this is affecting production systems and business operations, wouldn’t it be reasonable to expect at least some communication to App Creators about the status or investigation progress?
I see, apologies for not providing more clarity around this. That community post was raised internally on the 28th and escalated on Sep 1 as more reports came in. It looks like it took a few days of investigation to understand the issue and a few more to get a fix released (it went out yesterday). Updates were given on the internal bug ticket which would have been relayed to the individual customers that reported the bug through customer support, but I agree it would have been helpful to provide updates on the community post as well to reassure everyone reporting it here that it was being prioritized. I’ll keep that in mind next time I see a situation like that, and share this post with the broader team.
Hi @Adam-google ,
thank you for the detailed response and transparency about the internal escalation timeline. It’s reassuring to know the issue was prioritized internally.
I want to express special gratitude to you - you’re the only Google staff member who has been commenting on recent incident reports in the community. Your engagement is truly appreciated.
I also want to acknowledge @Trevor_Ryland who has been single-handedly providing status updates on this and other incidents. His contributions to keeping the community informed have been invaluable.
You’ve highlighted exactly what App Creators are looking for in this community - visibility into bug status and remediation efforts. Since support desk responses only reach individual customers who filed tickets, the community becomes our primary source for tracking widespread issues.
Would it be possible to provide more granular, real-time updates in community threads for critical bugs like this? Even brief status updates like “under investigation,” “fix in development,” or “deployment scheduled” would be incredibly valuable.
Have you considered utilizing the Google Workspace Status Dashboard for these types of service-impacting issues? The problems reported in the community over the past 2 weeks clearly qualify as business-critical incidents that affect operations.
The Google Workspace Dashboard supports RSS feeds, allowing App Creators to receive push notifications for the latest incident updates. This could provide significant value to the community and improve communication around platform stability.
Thanks again for engaging with the community on this.
Maybe Keep Silent is the policy and culture at Google AppSheet Team.
I believe there is little point in naming individuals. They can help sometimes, depending on their mood. A director-level person should get involved soon and train AppSheet internal employees to improve.
HI @Rifad ,
you’re absolutely right. Whenever I mention staff members in posts, they’re consistently ignored.
You make an excellent point about needing director-level involvement to address this communication gap.
Keeping the community informed about ongoing incidents should be a basic responsibility for any service provider, shouldn’t it? It’s standard practice across the industry, yet we’re left in the dark about issues affecting our production systems.
Having worked on that team, and with 10 years in this community, I can say that public communication and transparency are not priorities. The community is mostly an afterthought.