[SOLVED] Timeout not applied correctly

Hello Appwrite Community,

I set the timeout to 15 seconds on Appwrite Cloud, but the result still shows 5 seconds. Is this a bug or is it intended?

Kind Regards, Marius

TL;DR

The user had a question about the timeout on Appwrite Cloud. They set the timeout to 15 seconds but the result still shows 5 seconds. The community member explained that the timeout shown in the browser is not the same as the function timeout. They also mentioned that the keep alive timeout is a header for browsers to know when to hang up a request. The solution suggested was to change the number of timeout by sending a third parameter in res.send or res.json. Another community member asked if the user is running it in async. There is no clear resolution to the issue mentioned in the thread.

Are you running it in async?

Hey there 👋 Keep alive timeout is a geader for browsers to know when to hang up a request I believe. Appwtite isnt touching any headers so you have full freedom in what you build. My guess would be that this header comes vy default in http server library that we used to build runtime you are using.

To change this number, in res.send or res.json you can send 3rd parameter, which is object of all response headers you want and their values.

Timeout in function settings more connected to internal communication itself - allows you to ensure max durstion if 1 execution to let you better control usage (will be very useful when pricing is introduced on cloud)

Yes it runs in async, is this correct?

As Matej explained, the timeout being shown in the browser is not at all the function timeout

Thank you. Please mark as solved!