Synchronous function execution timed out. Use asynchronous execution instead, or ensure the executio

[tough grove]

Hi Appweite team !

I created an appwrite function in which I do API request to an AI server.
When request take long such as more than 30 secondes, the function execution fail and return below error, regardless of what timeout is set at function's setting page.
Synchronous function execution timed out. Use asynchronous execution instead, or ensure the execution duration doesn't exceed 30 seconds.\nError Code: 408

I call the function execution from another appwrite function using Node SDK.

I get this error when I call function execution with async => false.
I also get the error when I call the function execution using REST API (axios call to the functions's domain)

When I call the function execution with async => true, the execution hang at step "waiting" for up to 10mins or 15mins till I cancel the call then the execution pass to "processing" then "completed".

Appwrite version: 1.5.7
Appwrite node version: 12.0.1 (tried with 13.0.0 but getting import error)
SDK: Node 16 (tested with 18 and 20 also withe same result)

[short grail]

You need to set async to true. That is odd it's "waiting" for that long. Did you refresh the page to make sure?

Oh wait, on self-hosted, all async executions are queued and processed serially

[tough grove]

Hi I refreshed and also make so many try to make sure what is going on. I even restarted twice the server where appwrite installation is.

[tough grove]

Okay so, to make sure I understand: let's say I have 2 clients on my website and every client have a function dedicated to him and is executed every hours.

So what from what you said, every function execution will be queued and executed one after another ?

[tough grove]

Why the REST call execution using the domain also give same error ?
I mean, the doing curl api call, there is no such thing as async => true/false to settle.
So what is the point for this please ?
What I need in my function is to call an AI server and wait for this server to respond back then the remaining code can be executed accordingly.

[short grail]

Yes, all async executions are queued and are processed serially, unless you scale out the function workers.

[short grail]

All executions via domain are synchronous.

I suggest making the executions asynchronous and writing the response to a document that the user can read from. If you use realtime, you can get updates from your AI in realtime too depending on how you get the data

[tough grove]

Okay I see

So please, to make it very clear again, if my functions are settled for cron execution every hour, and say I have 30 functions, they will be queued all ?
So, let's say each function take 2mins to finish execution, then all the 30 functions will take 2mins x 30 (60mins) to be processed all, as they are all queued ? Is it ?

[ruby fable]

You can increase how many can processed at the same time

In regards to async execution

Add this _APP_WORKERS_NUMto the appwrite-worker-functions container env

Add _APP_WORKERS_NUMto your env file including the amount of workers like _APP_WORKERS_NUM=4. In this case 4 worker will process your async execution at the same time