Cloud Functions timeout, even though I've set the timeout settings to 900.
- 0
- Functions
- REST API
- Cloud
Hi,
I have a cloud function in the Appwrite cloud project. I noticed that my users receive an error response when their requests exceed 30 seconds.
However, I created a dummy cloud function to investigate with simple code that waits 40 seconds and returns dummy text. It returns an error after 30 seconds, even though I've set the timeout value to 900 seconds.
The dummy function:
Future<dynamic> main(final context) async {
await Future.delayed(Duration(seconds: 40));
return context.res.send('Hello, World!');
}
The error that I received in response:
Error 400
Internal error: Operation timed out after 30001 milliseconds with 0 bytes received
Type
general_argument_invalid
I'm calling the function using a RESTful API, and I'm using the cloud version of Appwrite. Also, I've set the timeout to 900 in the function's settings.
Just to verify, in Functions -> function -> settings -> timeout it says 900? I manually deploy most my functions and if you haven't updated the appwrite.json file when deploying it sets the timeout value back to the default.
Synchronous executions have a hard timeout of 30s
Are there any solutions to ensure that the function completes its execution within the timeout period?
Yes, I'm updating the timeout to 900 in the function settings whenever I make a new deployment
for slower functions, you should be executing them asynchronously
@VincentGe have we documented this yet?
Is this cloud specific? First time hearing about this
nope, not cloud specific
Recommended threads
- Triggers and call function in function p...
Hello, Today we are experiencing several issues with Appwrite Cloud. Functions triggered by events, or functions called from another function, are taking an e...
- Functions executed by events does not ap...
Hello, Running self-hosted Appwrite version 1.9.0 (with console 7.8.26). When functions are triggered by an event (eg. databases.\*tables.\*.rows.\*.create) doe...
- Updating GitHub App access throws error
Steps to reproduce - 1. Have some private repos allowed on the install access 2. New Site/Func > Connect GitHub > see the side card saying `Missing a repo` > cl...