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
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!
Btw, you can edit the title of your posts as well
[SOLVED] Timeout not applied correctly
Recommended threads
- Introducing new string column types made...
Adding new string types is hugely bennificial! Unfortunately it made the current column types not editable to change their types to the new longer field types.
- there is critical problem in this part
when user update the integer and double both get error not update or upload
- Appwrite docs mcp server 502 bad gateway
I added the appwrite docs mcp server to vscode following the docs https://appwrite.io/docs/tooling/mcp/vscode#step-1 but upon start it gives the following error...