This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Log in to ask a question

AppScript timeout when launched from AppSheet is not the same when launched from the Appscript IDE

Posted on 10-15-2024 12:33 AM
Vincent_Martin
Bronze 4
Bronze 4
Reply posted on --/--/---- --:-- AM

Hello,

When I launch a AppScript function from Appscript IDE or from GSheet, I have a 30mn timeout (Google Workspace account quota). But when it is launched from Appsheet automation in Asynchronous mode using my account, the timeout is 6mn (Public/Free account quota). I don't understand why ? The limitation is not from AppSheet, but in AppScript as timeout errors are all generated in AppScript log, not in AppSheet log

0 6 210
Topic Labels
0 Likes
6 REPLIES 6

Posted on --/--/---- --:-- AM
WillowMobileSys
Platinum 1
Platinum 1
Reply posted on --/--/---- --:-- AM

It isn't clear what you mean by "timeout".  Are you referring to the run time? 

Timeouts are typically errors indicating that the process stopped running either because itself ran too long OR it was waiting on another process that didn't respond in time.  

The typical timeout on an automation OVERALL is 5 minutes but each step within the automation is limited to 2 minutes.  

With this understanding, I have to assume you really are referring to run time.  If so, then the next question is WHERE are you getting this runtime value from?  Is it the AppSheet Monitor page or are you looking at the Script execution page?

Posted on --/--/---- --:-- AM
Vincent_Martin
Bronze 4
Bronze 4
In response to WillowMobileSys
Reply posted on --/--/---- --:-- AM

Thanks for your answer Willow

I really mean Timeout, not runtime. My automation step is launching an Appscript in asynchronous mode without any return value. In Synchronous mode (with return value), I saw that AppSheet generates an error after 2mn (as you said : timeout for a automation step).

When a step automation call an Appscript in asynchronous mode, AppSheet doesn't generate a timeout error. But the Appscript itself generates a timeout error after 6mn with this message in the AppScript IDE Cloud Log : 14 oct. 2024, 10:47:58 Error Exceeded maximum execution time.

So my question is : why there is a 6mn timeout in this AppScript when it is launched in asynchronous mode from AppSheet ? When I launch this script  from the AppScript IDE the timeout is 30mn !!

Is it clearer ? 

Posted on --/--/---- --:-- AM
Steve
Platinum 5
Platinum 5
Reply posted on --/--/---- --:-- AM

I'm not quite sure what you're looking for here. I myself would draw the conclusion that AppSheet imposes shorter timeouts in production than the App Script IDE imposes in development.

0 Likes

Posted on --/--/---- --:-- AM
Vincent_Martin
Bronze 4
Bronze 4
Reply posted on --/--/---- --:-- AM

For me, I always saw that AppScript timeouts from IDE (development) or hosted from GSheet (for example) in production were the same : 30mn for Google WorkSpace accounts. 6mn is for public/free accounts.
So I don't see why when it is launched by AppSheet it is now 6mn.  I just wonder if it is a bug, if AppScript is not launched by AppSheet using my Google Workspace account, but as a free or public account....

Posted on --/--/---- --:-- AM
maciej_nowak
Bronze 2
Bronze 2
In response to Vincent_Martin
Reply posted on --/--/---- --:-- AM

Hello, have you found solution/explaination of this matter? I am facing exactly the same which is an issue for the app designed in AppSheet. Best regards.

0 Likes

Posted on --/--/---- --:-- AM
Vincent_Martin
Bronze 4
Bronze 4
In response to maciej_nowak
Reply posted on --/--/---- --:-- AM

I have no explaination of this. I suppose it is a Google policy. The work around is to use timer event and split the task in several limited jobs