Methods for Early Detection of AppSheet System Failures and Report Confirmation

[11198]

I am currently providing applications built with AppSheet to my clients.

When an AppSheet system failure occurs, I want to establish a method for quickly detecting and addressing the issue before the client contacts me.

Additionally, in the event of a failure, I would like to collect information and reports regarding the incident so I can later clearly explain the cause to my clients.

While I already know several methods to collect information, I want to ensure I am aware of all possible methods comprehensively. I believe there may be additional methods I am unaware of, so I am seeking advice from the community.

---

① Methods for Detecting Failures

• Please share the methods you use to quickly grasp the situation and scope of impact when an AppSheet system failure occurs.

② Methods for Gathering Detailed Information about Failures

• Please provide specific methods for obtaining detailed information (e.g., cause and impact range) about system failures.

③ Notifications from AppSheet Regarding Failures

• Does AppSheet provide a built-in mechanism to notify users or administrators directly when a system failure occurs?

④ Creative Approaches Using GAS or Automation for Failure Detection

• If you have implemented or know of creative user-side methods for detecting AppSheet failures, please share specific examples or ideas.

• As a practical example, I am considering using AppSheet Automation (Bot) to regularly output data to a spreadsheet. Then, separately running Apps Script  periodically to check the spreadsheet. If the spreadsheet data isn't updated within a certain timeframe, it could indicate a possible system issue.

---

Early detection and rapid response to failures are crucial for maintaining trust with clients.

I would greatly appreciate hearing your insights and examples.
Thank you very much.