Can't contact Support - Contact Us button disappears and form doesn't load

Hi,

I’m trying to contact support. After clicking the “Contact us” button, I’m redirected to the same page but the “Contact us” button has disappeared. I was able to contact support a few days ago.

I’ve tried clearing cache and cookies, opening in an incognito window, opening in another browser, but they all lead to the same issue.

Here are the console errors when loading the page:

Uncaught (in promise) Error: Q
at pi (appsheet/?sjid=16347703352275418467-NC&visit_id=639108346256743149-3253491823&rd=1:196:259)
at new X (appsheet/?sjid=16347703352275418467-NC&visit_id=639108346256743149-3253491823&rd=1:205:500)
at appsheet/?sjid=16347703352275418467-NC&visit_id=639108346256743149-3253491823&rd=1:212:220
at appsheet/?sjid=16347703352275418467-NC&visit_id=639108346256743149-3253491823&rd=1:224:3Understand this error
/appsheet/?sjid=1634…=1#topic=10101310:1 Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was receivedUnderstand this error
Navigated to AppSheet Help
appsheet/?sjid=16347703352275418467-NC&visit_id=639108346256743149-3253491823&rd=1:196 Uncaught (in promise) Error: Q
at pi (appsheet/?sjid=16347703352275418467-NC&visit_id=639108346256743149-3253491823&rd=1:196:259)
at new X (appsheet/?sjid=16347703352275418467-NC&visit_id=639108346256743149-3253491823&rd=1:205:500)
at appsheet/?sjid=16347703352275418467-NC&visit_id=639108346256743149-3253491823&rd=1:212:220
at appsheet/?sjid=16347703352275418467-NC&visit_id=639108346256743149-3253491823&rd=1:224:3

cc @Jose_Arteaga

This suggests you are not or are no longer a paying customer, as support is only available to paying customers.

Our most recent payment was paid on 3/12/2026.

Hello @kennysz,

My apologies for the inconvenience. I’ll send you a PM in the next few minutes.

2 Likes

Hello @kennysz, I have escalated it to the engineering team for further analysis. I will keep you posted!

2 Likes

Hello @kennysz, I got an update that the issue has been resolved. Can you please check and confirm.
Thank you!

Yes, this issue is now resolved. Thanks!

2 Likes