Error loading App Script Project info: Null response received from server

Can´t connect to AppScript from AppSheet. 

Captura de pantalla 2024-09-10 a la(s) 18.35.20.png

0 10 623
10 REPLIES 10

can confirm i am getting this as well.  getting a 500 from the server

 

{
"ClassName": "System.Exception",
"Message": "Null response received from server",
"Data": null,
"InnerException": null,
"HelpURL": null,
"StackTraceString": null,
"RemoteStackTraceString": null,
"RemoteStackIndex": 0,
"ExceptionMethod": null,
"HResult": -2146233088,
"Source": null,
"WatsonBuckets": null
}

Yes, we are facing the same issue. Obviously outage seems to be happening to connect to GAS resources from AppSheet.  

@lizlynch 

@willwitman 

@nico @isdal 

@devingu 

Can you have a look?

2024-09-11_09-51-11.PNG

 

Hi @Koichi_Tsuji ,

Same here, hope there is a solution soon.

Yes, we are are aware of the issue affecting the AppSheet Apps Script integration and are actively working to resolve it (we have many on-calls working on the issue as we speak).

It's the same issue that's affecting the licensing service and a few other services we're using. We are waiting for approval from another team and are trying to get this resolved ASAP. Sorry for the feature outage here -- expect it to be resolved shortly.

Thanks @nico for your quick response.

Does this issue affect to the ongoing live app where the app script task is pushed into the BOT ? or only affecting to the new connection to the GAS file from appsheet?

This outage affects both adding new Apps Script Tasks and the Apps Script execution itself (within AppSheet), unfortunately. We are obviously treating this as an urgent incident so expect resolution within the next few hours here.

Thanks noted.

We have bunch of existing apps integrating with GAS .... Hopefully this bug will be fixed soonest.  Can you give us a head up here once the issue is fixed so that we can test with our apps?

Thanks

It appears the outage has now been resolved - our alerts are recovering. Apologies for the issue.

@nico 

Thank you for the update.  We tested with our apps and confirmed it got back to normal behavior. Thanks again.

@AleksiAlkio 

Could you relay to the dev team to give a head up?