Assigned
Status Update
Comments
gk...@google.com <gk...@google.com> #2
Converting to an enhancement request.
st...@gmail.com <st...@gmail.com> #3
Any update on the status of this enhancement?
gr...@sutherland.id <gr...@sutherland.id> #4
Fails for UrlFetches to far-away places like China. Making it configurable would be useful -- or reporting it as an actual timeout would help as well.
[Deleted User] <[Deleted User]> #5
I also need this feature, any update on the status ?
[Deleted User] <[Deleted User]> #6
Any update?
bs...@gmail.com <bs...@gmail.com> #7
Any update on this feature request, Its really important for us to have this feature
gr...@websawin.com <gr...@websawin.com> #8
I'm seeing the opposite issue lately. The UrlFetchApp.fetch call is taking far too long, the worst today is 257sec. I'd like to set a 10-30sec timeout and stop these calls from using up all of my time-based quotas. There must be an issue with this function as manually calling these urls is much faster, typically a second or less.
ch...@gmail.com <ch...@gmail.com> #9
Yes, I need a configurable timeout to prevent a single long running fetch from eating up all the time-based quota.
ma...@gmail.com <ma...@gmail.com> #10
@ g...@websawin.com
I see the same bahaviour, that the timeout happens now after several minutes.
Also my UrlFetchApp.fetch() call aborted after more than 4 Minutes (!) today with an timeout!
According to the google error mail ("summary of failures of google apps script"), there must be also UrlFetchApp.fetch() calls taking more than 9 Minutes ("script exceeded maximum execution time").
This is consuming up all my daily CPU-time, very frustating :-((
I see the same bahaviour, that the timeout happens now after several minutes.
Also my UrlFetchApp.fetch() call aborted after more than 4 Minutes (!) today with an timeout!
According to the google error mail ("summary of failures of google apps script"), there must be also UrlFetchApp.fetch() calls taking more than 9 Minutes ("script exceeded maximum execution time").
This is consuming up all my daily CPU-time, very frustating :-((
[Deleted User] <[Deleted User]> #11
This would be a great feature, since max execution time for a trigger is 1h or 3h a day in pro plan and if a ressource doesn't respond it does eventually timeout after 5 minutes. It would be much better if we could timeout the request and try later to better optimize our ressources.
[Deleted User] <[Deleted User]> #13
[Comment deleted]
[Deleted User] <[Deleted User]> #14
Any update on this feature request? Would help out a lot within a very large and important application. Thanks.
rs...@gmail.com <rs...@gmail.com> #15
yes, I need the same. Yes, please increase timeout to 5 mins at least.
jp...@gmail.com <jp...@gmail.com> #16
It's hard to take App Script as a serious framework when this basic functionality is missing...
jm...@gmail.com <jm...@gmail.com> #17
a single fetch that times out eats up a good chunk of the time quota and makes a script run slow. Time out needs to be configurable
ro...@suisseo.ch <ro...@suisseo.ch> #18
[Comment deleted]
[Deleted User] <[Deleted User]> #19
Would really need this enhancement too
bh...@gmail.com <bh...@gmail.com> #20
Yes, please I need this too.
di...@speedio.com.br <di...@speedio.com.br> #21
I need this functionality. We were moving our code from vba to google app script, now with this limitation we can´t.
gl...@gmail.com <gl...@gmail.com> #22
Also need to be able to decrease this! When a website is down, the long timeouts can kill the computer time quota for the day, rendering my script useless!
an...@maxlead.com <an...@maxlead.com> #23
Same here. A must have, also making timeout shorter (for services that take a long time to send a response. This in conjunction with max execution time of 5 minutes. Thanks.
da...@gmail.com <da...@gmail.com> #24
Same comment as others. If a service goes offline, it can chew up your quota for the day very quickly.
[Deleted User] <[Deleted User]> #25
I really need this extension too.
Configurable timeout would be preferred, even though I would manage with just extending the timeout.
Configurable timeout would be preferred, even though I would manage with just extending the timeout.
4a...@gmail.com <4a...@gmail.com> #26
Any update?
ry...@google.com <ry...@google.com>
[Deleted User] <[Deleted User]> #27
Is this still not implemented?
ik...@gmail.com <ik...@gmail.com> #28
I have the same problem. Need to have configurable timeout
sh...@gmail.com <sh...@gmail.com> #29
it saddens me that this discussion has gone on for 3 years - has this really not be solved yet!? this is a key feature that I need to use scripts in a real system, please add some level of configurability for timeouts!
po...@gmail.com <po...@gmail.com> #30
Any updates on this yet ? Wondering why is this so difficult ?
em...@gmail.com <em...@gmail.com> #31
Seems that the timeout feature is not yet implemented (3 years since the first change request).
Is there maybe a workaround to overcome this issue?
Is there maybe a workaround to overcome this issue?
ad...@igbis.edu.my <ad...@igbis.edu.my> #33
With the advent of UrlFetchApp.fetchAll, being able to manage timeouts becomes even more of an issue. It's basically broken behaviour to have it timeout without any way of handling it, and now with fetchAll any one of those requests timing out will render the whole operation as having timed out.
ga...@incentfit.com <ga...@incentfit.com> #34
I agree. This is not a FeatureRequest, it's really a bug...
nj...@gmail.com <nj...@gmail.com> #35
Any update on this? This is really important feature.
[Deleted User] <[Deleted User]> #36
Is there any update on this?
[Deleted User] <[Deleted User]> #37
Anyone? Beuler? This has been open for 4+ years with no motion yet continues to cause problems for many.
su...@happay.in <su...@happay.in> #38
Any updates ?
ma...@gmail.com <ma...@gmail.com> #39
If Add-on cross the execution timing(above 30s) throw the exception, how to handle these error message. Because I'm using try/catch again same issue rises.
ca...@gmail.com <ca...@gmail.com> #40
+1 - being able to manually time out fetch requests would be ideal.
scenario: fetching several URLs, one request tries to fetch an unresponsive site. the script is suspended until the response is returned, which usually takes over 1 minute.
it would be so helpful to be able to set a time to return the fetch request, even without a response.
thanks!
scenario: fetching several URLs, one request tries to fetch an unresponsive site. the script is suspended until the response is returned, which usually takes over 1 minute.
it would be so helpful to be able to set a time to return the fetch request, even without a response.
thanks!
ma...@gmail.com <ma...@gmail.com> #41
This would be EXTREMELY useful!
PLEASE IMPLEMENT THIS, PRETTY PRETTY PLEASE!!!!
PLEASE IMPLEMENT THIS, PRETTY PRETTY PLEASE!!!!
am...@gmail.com <am...@gmail.com> #42
I'm getting a 1 minute timeout for requests in data studio. Please allow to extend the timeout!
ge...@gmail.com <ge...@gmail.com> #43
Yes, I also need to configure the timeout. I'm working with GAS for requesting the Google URL Testing Tools API. It takes around 1-1,5min to get all data (performing the screenshot).
ma...@gmail.com <ma...@gmail.com> #44
I am new to Gmail Add-ons, facing the timeout issue UrlFetchApp.fetch() method. Cross the time limit call particular API in above 60s at this time doesn't handle the exceptions, also using the try/catch but doesn't handle.How is it over come this?
Sorry for my bad English.
Sorry for my bad English.
dc...@gmail.com <dc...@gmail.com> #45
I would prefer we get a parameter to adjust it, as for standard HTTP requests 1 minute is an eternity.
Something to the tune of UrlFetchApp.fetch('https://www.google.com ', { timeout: 3000 }) much like the already existing UrlFetchApp.fetch('https://www.google.com ', { muteHttpExceptions: true})
Something to the tune of UrlFetchApp.fetch('
fd...@gmail.com <fd...@gmail.com> #46
Keep dreaming. This is almost 6 years old. I don't understand why Google doesn't simply mark this as "won't fix", but it does not surprise me, I am subscribed to several issues in the same situation for years.
le...@gmail.com <le...@gmail.com> #47
any updates ? ;-)
xa...@featherfinance.com <xa...@featherfinance.com> #48
+1
Would love to have more granular control / visibility on timeout
Would love to have more granular control / visibility on timeout
pa...@gmail.com <pa...@gmail.com> #49
+1
gs...@gmail.com <gs...@gmail.com> #50
And here we are in 2020 without so much as a single response from Google. Hello, testing, 1, 2, 3. Is this thing on?
kn...@gmail.com <kn...@gmail.com> #51
+1
In case it hasn't been said already (in the many, many comments), I need to be able to LIMIT the time, not extend it.
In case it hasn't been said already (in the many, many comments), I need to be able to LIMIT the time, not extend it.
an...@gmail.com <an...@gmail.com> #52
I have the same request.
I also want to LIMIT the timeout. Not extend it.
My script makes calls to an IoT device, which is sometimes offline.
UrlFetchApp.fetch expires at around 50 seconds. If my device is online, it would respond within 2 seconds required for the entire script to complete.
Even with a conservative timeout, I can set it to 5 seconds and my device would respond within that time, if online. If it doesn't I don't wish to continue trying for another 45 seconds.
At present, because of the global quota of 90 mins/day, I have to limit my trigger frequency accordingly.
I also want to LIMIT the timeout. Not extend it.
My script makes calls to an IoT device, which is sometimes offline.
UrlFetchApp.fetch expires at around 50 seconds. If my device is online, it would respond within 2 seconds required for the entire script to complete.
Even with a conservative timeout, I can set it to 5 seconds and my device would respond within that time, if online. If it doesn't I don't wish to continue trying for another 45 seconds.
At present, because of the global quota of 90 mins/day, I have to limit my trigger frequency accordingly.
dw...@calance.us <dw...@calance.us> #53
Same here, allow us to configure the timeout. In my case I want to shorten it, but that is irrelevant to fixing the problem.
ak...@gmail.com <ak...@gmail.com> #54
What the heck google? 6 years and no response.
al...@sada.com <al...@sada.com> #55
This still isn't done? LMAO!
ja...@cs-hk.com.hk <ja...@cs-hk.com.hk> #56
"Unexpected error : Timeout http://blablabla. ..." Occur
I am not sure as same but its similar . My script was fetch the large report(html text only) as blob/html file and save it in drive. The little trick is error should occur after 3 minutes every time during fetching, I added line "cache-control": "max-age=0" in header during fetch, no more error and the file fetched. Problem is the fetch was seems still stopped on every 3 minutes, affect the html file incomplete. So what is going on.
My Log:
[20-11-11 20:17:40:174 PST] Before Fetch
[20-11-11 20:20:40:209 PST] After Fetch
My script :
//The script is working if smaller size report to fetch and complete within 3 minutes.
//some dataOptions may not necessary
function myfun(){
var dataURL = 'https://someblablabla/report.php ';
let form = "some payload here";
const dataHeaders = {
"cache-control": "max-age=0",
'Cookie' : "some cookie like login id/pw",
'Origin' : 'https://someblablabla '
};
const dataOptions = {
'Host' : 'someblablabla',
'method':'get',
'timeout' : '0',
'contentType': 'application/x-www-form-urlencoded',
'headers':dataHeaders,
'payload' : form,
'useIntranet': false,
'validateHttpsCertificates': true,
'followRedirects' : true,
'mode': 'navigate',
'muteHttpExceptions' : true,
'Transfer-Encoding': 'chunked'
};
Logger.log("Before Fetch")
var dataResponse = UrlFetchApp.fetch(dataURL,dataOptions);
Logger.log("After Fetch")
var data = dataResponse.getAs('text/html');
var folder = DriveApp.getFolderById('yourfolderid');
folder.createFile(data);
}
I am not sure as same but its similar . My script was fetch the large report(html text only) as blob/html file and save it in drive. The little trick is error should occur after 3 minutes every time during fetching, I added line "cache-control": "max-age=0" in header during fetch, no more error and the file fetched. Problem is the fetch was seems still stopped on every 3 minutes, affect the html file incomplete. So what is going on.
My Log:
[20-11-11 20:17:40:174 PST] Before Fetch
[20-11-11 20:20:40:209 PST] After Fetch
My script :
//The script is working if smaller size report to fetch and complete within 3 minutes.
//some dataOptions may not necessary
function myfun(){
var dataURL = '
let form = "some payload here";
const dataHeaders = {
"cache-control": "max-age=0",
'Cookie' : "some cookie like login id/pw",
'Origin' : '
};
const dataOptions = {
'Host' : 'someblablabla',
'method':'get',
'timeout' : '0',
'contentType': 'application/x-www-form-urlencoded',
'headers':dataHeaders,
'payload' : form,
'useIntranet': false,
'validateHttpsCertificates': true,
'followRedirects' : true,
'mode': 'navigate',
'muteHttpExceptions' : true,
'Transfer-Encoding': 'chunked'
};
Logger.log("Before Fetch")
var dataResponse = UrlFetchApp.fetch(dataURL,dataOptions);
Logger.log("After Fetch")
var data = dataResponse.getAs('text/html');
var folder = DriveApp.getFolderById('yourfolderid');
folder.createFile(data);
}
to...@gmail.com <to...@gmail.com> #57
me too.. why urlfetch has timeout ,..p lease extend..
xa...@gmail.com <xa...@gmail.com> #58
I would like configuration too. Stops a single request going for 100 seconds and eating too much of my time execution quota.
ji...@soonercentral.net <ji...@soonercentral.net> #59
I too would like to see an option to control timeout, not so much to extend but shorten.
cr...@gmail.com <cr...@gmail.com> #60
Let's go for a 10 year long ticket, shall we? :)). Obviosuly I could use a timeout option as well.
ch...@gmail.com <ch...@gmail.com> #61
+1 for 10y long ticket ;) . I need the timeout as well obviously.
an...@catenamedia.com <an...@catenamedia.com> #62
Comment has been deleted.
an...@kiwidrew.com <an...@kiwidrew.com> #63
This is the issue that keeps on giving! It's my semi-regular reminder that I really dodged a bullet when deciding not to use Apps Script for anything serious. It's obvious that Apps Script was created merely to tick a box in the feature list so the sales guys could claim GApps had feature parity with Microsoft's offerings.
Good luck petitioning the gods to implement this feature. I'll eat a sock if this ticket ever gets an official Google response.
Good luck petitioning the gods to implement this feature. I'll eat a sock if this ticket ever gets an official Google response.
me...@gmail.com <me...@gmail.com> #64
+1
bo...@gmail.com <bo...@gmail.com> #65
+1, One of the main reasons why i'll be switching away from apps script
bo...@gmail.com <bo...@gmail.com> #66
+1, can't believe it is not resolved yet !
sh...@gmail.com <sh...@gmail.com> #67
+1
ri...@thenymans.net <ri...@thenymans.net> #68
+1 (again)
Just checking back to make sure that there isn't any progress on this. I'm locked at a 6 minute timeout - would love to make it lower.
Just checking back to make sure that there isn't any progress on this. I'm locked at a 6 minute timeout - would love to make it lower.
ma...@gmail.com <ma...@gmail.com> #69
+1 Interested in this as well
cr...@gmail.com <cr...@gmail.com> #70
+1
an...@gmail.com <an...@gmail.com> #71
+1
jo...@gmail.com <jo...@gmail.com> #72
+1
ht...@gmail.com <ht...@gmail.com> #73
7 years later...
sj...@en-masse.nl <sj...@en-masse.nl> #74
+1
di...@mercadolibre.com <di...@mercadolibre.com> #75
+1
ma...@gmail.com <ma...@gmail.com> #76
+1
sc...@gmail.com <sc...@gmail.com> #77
+1
ar...@gmail.com <ar...@gmail.com> #78
+1
[Deleted User] <[Deleted User]> #79
Comment has been deleted.
[Deleted User] <[Deleted User]> #80
+1
st...@gmail.com <st...@gmail.com> #81
This would be real helpful
zi...@gmail.com <zi...@gmail.com> #82
+1
la...@crowdsec.net <la...@crowdsec.net> #83
This would be real helpful +1
in...@daprfashion.nl <in...@daprfashion.nl> #84
(Y)
pr...@iihs.ac.in <pr...@iihs.ac.in> #85
+1
ma...@gmail.com <ma...@gmail.com> #86
+
mo...@okgtech.com <mo...@okgtech.com> #87
+1
ar...@gmail.com <ar...@gmail.com> #88
+1
ap...@icloud.com <ap...@icloud.com> #89
+1
mi...@gmail.com <mi...@gmail.com> #90
+1
ma...@e-hps.com <ma...@e-hps.com> #91
+1
[Deleted User] <[Deleted User]> #92
+1
ch...@ex.mavenwave.com <ch...@ex.mavenwave.com> #93
I reached out to Workspace support and they do in fact have an internal feature request for this issue. Internally, the request is #131685592. If you have connections with Google Support, they should be able to provide updates on the status of this feature.
As of today, the request has been routed to the product engineering team but they have not provided an ETA for a solution.
As of today, the request has been routed to the product engineering team but they have not provided an ETA for a solution.
ri...@gmail.com <ri...@gmail.com> #94
+1
an...@gmail.com <an...@gmail.com> #95
+1
al...@gmail.com <al...@gmail.com> #96
+1
ms...@datostecnicos.com <ms...@datostecnicos.com> #97
+1
bu...@gmail.com <bu...@gmail.com> #98
+1
co...@gmail.com <co...@gmail.com> #99
+1
al...@gmail.com <al...@gmail.com> #100
+1
g....@gdev.inc <g....@gdev.inc> #101
Comment has been deleted.
al...@gmail.com <al...@gmail.com> #102
We need a configurable timeout as well as async downloading without the complexities of FetchAll. The year is 2022.
zo...@gmail.com <zo...@gmail.com> #103
+1
[Deleted User] <[Deleted User]> #104
+1
se...@gmail.com <se...@gmail.com> #105
+1 much needed over here
[Deleted User] <[Deleted User]> #106
+1
ph...@gmail.com <ph...@gmail.com> #107
+1
ce...@veolia.com <ce...@veolia.com> #108
+1
ps...@gmail.com <ps...@gmail.com> #109
+1
ya...@gmail.com <ya...@gmail.com> #110
+1
g2...@gmail.com <g2...@gmail.com> #111
Comment has been deleted.
va...@gmail.com <va...@gmail.com> #112
+1
an...@zero-one-group.com <an...@zero-one-group.com> #113
+1
[Deleted User] <[Deleted User]> #114
+1
ro...@gmail.com <ro...@gmail.com> #115
+1
tr...@troyfawkes.com <tr...@troyfawkes.com> #116
+1
na...@aljazeera.net <na...@aljazeera.net> #117
+1
ci...@gmail.com <ci...@gmail.com> #118
Comment has been deleted.
da...@gmail.com <da...@gmail.com> #119
+1
an...@gapless-app.com <an...@gapless-app.com> #120
+1
[Deleted User] <[Deleted User]> #121
+1
kn...@gmail.com <kn...@gmail.com> #122
My god.
I wrote this ticket almost 9 YEARS ago.
It has 139 upvotes (and counting) and over 100 supporting comments.
WHADDAYA HAVE TO DO?
I wrote this ticket almost 9 YEARS ago.
It has 139 upvotes (and counting) and over 100 supporting comments.
WHADDAYA HAVE TO DO?
ji...@soonercentral.net <ji...@soonercentral.net> #123
^^ And I'm still following it hoping they "eventually do something".
ch...@gmail.com <ch...@gmail.com> #124
Hello from 2023
ph...@prompt.io <ph...@prompt.io> #125
upvote
rb...@gmail.com <rb...@gmail.com> #126
+1
ya...@gmail.com <ya...@gmail.com> #127
+1
pa...@bci.cl <pa...@bci.cl> #128
+1
s....@sporting-comm.fr <s....@sporting-comm.fr> #129
yeah that or axios library
it...@amazinga.fun <it...@amazinga.fun> #130
+1
ak...@gmail.com <ak...@gmail.com> #131
+1
[Deleted User] <[Deleted User]> #132
+1
de...@gmail.com <de...@gmail.com> #133
+1
[Deleted User] <[Deleted User]> #134
+1
my...@gooselaw.com <my...@gooselaw.com> #135
+1
sw...@gmail.com <sw...@gmail.com> #136
+1
Need to limit.
Need to limit.
[Deleted User] <[Deleted User]> #137
+1
ti...@triband.net <ti...@triband.net> #138
+1
[Deleted User] <[Deleted User]> #139
+1
ro...@oichuy.com.br <ro...@oichuy.com.br> #140
+1
sh...@valeo.com <sh...@valeo.com> #141
+1
lu...@innovar.app <lu...@innovar.app> #142
+1
yo...@gmail.com <yo...@gmail.com> #143
+1
an...@quantuna.com <an...@quantuna.com> #144
This is freaking pathetic :D
mi...@gmail.com <mi...@gmail.com> #145
+1
ja...@gmail.com <ja...@gmail.com> #146
+1
an...@gmail.com <an...@gmail.com> #147
+1
mi...@leasity.cl <mi...@leasity.cl> #148
+1
fr...@leasity.cl <fr...@leasity.cl> #149
+1 Please we need this feature asap
sa...@dexterity.ai <sa...@dexterity.ai> #150
Comment has been deleted.
na...@gmail.com <na...@gmail.com> #151
At least it's assigned... will it ever get delivered? Does the person this was assigned to even still work at Google?
ch...@gmail.com <ch...@gmail.com> #152
Relative to the age of the universe, a decade (soon) is still within the realm of ASAP...
I've stopped developing in Apps Script for a long time (I'm comment #9 ) but this thread keeps reminding me what I once knew :D
I've stopped developing in Apps Script for a long time (I'm
ca...@gmail.com <ca...@gmail.com> #153
Please i need this lo necesitamos, incrementen el tiempo de llamado a fetchURl
da...@gmail.com <da...@gmail.com> #154
+1
eq...@gmail.com <eq...@gmail.com> #155
I need to reduce timeout to avoid losing time.
+1
+1
st...@gmail.com <st...@gmail.com> #156
+1
am...@bglcorp.com.au <am...@bglcorp.com.au> #157
+1
ed...@egsc.com.br <ed...@egsc.com.br> #158
+1
ka...@gmail.com <ka...@gmail.com> #159
+1
or...@gmail.com <or...@gmail.com> #160
+1
dp...@stanford.edu <dp...@stanford.edu> #161
+1
va...@gmail.com <va...@gmail.com> #162
+1
na...@gmail.com <na...@gmail.com> #163
OpenAI API takes too long to respond, we all need this to accommodate the GPT hype train!!!!
ma...@gmail.com <ma...@gmail.com> #164
+1
in...@looplabz.com <in...@looplabz.com> #165
+1 I want to control time out because App Script (Spreadsheet) has a 6 mins timeout. And I want to make sure I'll not hit that limit.
GPT Sometimes takes too long for the answer
GPT Sometimes takes too long for the answer
fd...@jin.fr <fd...@jin.fr> #166
+1
ju...@redabacusdesign.com <ju...@redabacusdesign.com> #167
It would be better to have the timeout as a param/option to the fetch function.
Sometimes I might expect a request to fail fast and continue with another path.
Sometimes I might expect a request to fail fast and continue with another path.
ma...@airporting.com <ma...@airporting.com> #168
+1
an...@modmed.com <an...@modmed.com> #169
+1
da...@gmail.com <da...@gmail.com> #170
+1
ju...@linkconsulting.com <ju...@linkconsulting.com> #171
+1
[Deleted User] <[Deleted User]> #172
+1
ma...@distantfield.space <ma...@distantfield.space> #173
+1
av...@gmail.com <av...@gmail.com> #174
+1
kr...@deptagency.com <kr...@deptagency.com> #175
+1
os...@carvuk.com <os...@carvuk.com> #176
+1 plsssss
ja...@gmail.com <ja...@gmail.com> #177
We're actually going to hit 10 years for this request. And a decently popular request at that.
+1
+1
bu...@gmail.com <bu...@gmail.com> #178
+1
de...@websheet.cc <de...@websheet.cc> #179
+1
wo...@gmail.com <wo...@gmail.com> #180
+1
th...@gmail.com <th...@gmail.com> #181
+100!
va...@gmail.com <va...@gmail.com> #182
It's 10 years now! 🎉
ma...@gmail.com <ma...@gmail.com> #183
Happy 10th anniversary of this bug everyone! 🥳
ag...@philasd.org <ag...@philasd.org> #184
Would be great to have this as a customizable option. I want to call a Google Apps script web App, from a GAS UI script on a spreadsheet. It specifically involves the creation of a large Google Document (with a lot of images) so this can take a long time. Using a Web App will allow me to run the script as myself, and access folders I wouldn't necessarily want to give the user access to (which they would need in order to create a document in the folder). It also allows me to hide parts of the code, like an API key for an external service.
In the mean time, I would have to use a workaround of expecting the URLFetch to fail, ignoring the failure message, and updating the spreadsheet via the web App with some kind of value that could be checked for in a loop by the UI script. This makes seeing when there is actually an error with the URLFetch a lot harder to do.
Thank you for your time and help!
In the mean time, I would have to use a workaround of expecting the URLFetch to fail, ignoring the failure message, and updating the spreadsheet via the web App with some kind of value that could be checked for in a loop by the UI script. This makes seeing when there is actually an error with the URLFetch a lot harder to do.
Thank you for your time and help!
[Deleted User] <[Deleted User]> #185
+1
ma...@aodb.com <ma...@aodb.com> #186
+1
el...@gmail.com <el...@gmail.com> #187
Can the assigned user gives us some update notes on this issue? ap...@google.com
is...@sparta.cl <is...@sparta.cl> #188
+1
na...@gmail.com <na...@gmail.com> #189
+1
re...@gmail.com <re...@gmail.com> #190
+1
un...@gmail.com <un...@gmail.com> #191
+1
[Deleted User] <[Deleted User]> #192
There ain't no way this is still not a thing?!? Any basic engineer needs this
sy...@gmail.com <sy...@gmail.com> #193
+1
di...@gmail.com <di...@gmail.com> #194
+1 not having this is a nightmare. Having to implement all sorts of complex AWS Lambda router functions that handle the timeout. Hate it.
go...@gdn.com.uy <go...@gdn.com.uy> #195
+1
10 years since it was created, not having this is a nightmare.
10 years since it was created, not having this is a nightmare.
pa...@gdn.com.uy <pa...@gdn.com.uy> #196
+1
kr...@gmail.com <kr...@gmail.com> #197
+1 wait
se...@gmail.com <se...@gmail.com> #198
+1
ma...@gmail.com <ma...@gmail.com> #199
+1
ca...@quinyx.com <ca...@quinyx.com> #200
+1
co...@nervaenergy.com <co...@nervaenergy.com> #201
+1
Description
I am fetching a JSON object from an Internet of things device with the following code:
var sensor = UrlFetchApp.fetch("
70% of my requests timeout as I am fetching data from a relative slow IoT device.
Can you add an option to the fetch command to allow larger timeouts?