Thank you very much for your reply.
I hope you will receive good news as soon as possible.
Thank you for your continued support.
2 Likes
Tsuji I share your frustrations. As someone that’s building software that companies literally run on - mission critical stuff here - it adds difficulty to the process when there’s an error on the AS side of things, and there’s little transparency as to what’s going on.
We’re looking at things from the user perspective; if you put your business hat on and look at it from that side… if they were to have an accurate and honest running list of all the issues, outtages, etc. - what sort of image would that present?
Now… if they embraced it, leaning into the fact that they’re building a software system… humans are imperfect… mistakes will be made, but we fix them ASAP!!! We’re tightly engaged with our community, etc. etc.
- You remember what the community was like in 2018?
- Devs here answering questions directly; especially here during the daily rollout, to catch all the issues people report.
- Those times were great. When something popped up, we could say something and someone ON THE ACTUAL DEV TEAM would chime in with the answer. OMG, it was great. Problems were solved almost immediately.
If we could get back to something like that, man… that would go a LONG way - and present such a strong positive front image to potential new businesses that are thinking of migrating their systems to AS.
I will say: it does seem that the trusted community expert escalation thing works well. Whenever I submit something through that, it’s escalated pretty quickly.
6 Likes
The outage on Apps Script executions over 60s should be resolved by the end of day today. It’s already successful for over 50% of 60s< requests but the remaining 50% should be rolling out today - we’re waiting on a server config rollout to complete which is slow.
6 Likes
Thank you! 
2 Likes
Requests over 60s has been fully fixed according to logs as of yesterday – thanks for your patience.
4 Likes
We confirmed that processes exceeding 60 seconds are not canceled.
Thank you very much.
3 Likes
Thanks for getting a fix in place, and for the updates and transparency. 
2 Likes
My app seems to still be having the issue but now the time limit is 120s instead of 60s.
The 120s timelimit is for bots triggered from events. See: Automation Limits
The limit is increased to 5 minutes if you want to run a scheduled bot instead.
2 Likes