Skip to main content

Hi folks,

I am testing a scenario for a simple action wherein the action will result in timeout based on the Script Timeout parameter set by the developer. Currently, I have an action that sleeps for around 59.9 seconds but my Script Timeout value is 30 seconds. Ideally, this action should timeout and fail, but somehow, it shows the max timeout value as 59 seconds in the output (screenshot 2).

 

As seen in the screenshot below, the error shows the max limit of execution as 59 seconds instead of 30 seconds. 

Also, when I use sleep in the action for 59 seconds (and not 59.9), the action passes and Debug Output shows a successful message. This shows that the script does not adhere to the Script Timeout parameter. How should I correct this behaviour ??

Thanks.

  

@preet_mehta I believe it is a platform behaviour when it adds ~30 seconds to the Script Timeout to make sure that your script will be finished. If this is concerning you as a behaviour I would recommend to open a Support Ticket in order to confirm this behaviour and see if it is possible to change it for specific scenario. 


Also, I'm wondering, what a usecase you have when you need to have a timeout exactly 30 seconds and not above? If possible could you please share details about it so maybe I will be able to propose you a solution. 

Hi @f3rz Thanks for the insight.

I do not have a particular usecase for a 30 second timeout, but I need to document this feature of Script Timeout for my integration's end users and I just noticed this inconsistency, hence the concern. If the platform does add ~30 seconds, then I can document it to make sure the users are already aware of this case.

Thanks.

Reply


Terms & ConditionsCookie settings
Privacy Policy Terms of Service Gen AI Policy Community Guidelines Cookie Settings

© 2025 Google. All rights reserved.