Function Execution timed out

i wonder if the error coincides with:

Skipping runtimes stats loop due to error: Docker Error: EOF

Also, any logs in the runtime container?

@Drake what is the name of that container? I can't find it.

<project id>-<deployment id>

@Drake there is no container with that name

you might need to execute it to spin it up again

@Drake I checked for three functions but there are no logs

I get the same behavior when self-hosting on my local pc. Usually after a docker compose up, the functions will keep timing out. Then after like 10 minutes, it suddenly starts working again.

It also started happening on my self-hosted production server, but I managed to fix it by upgrading to 2 vcpu cores, almost like there was a deadlock somewhere. Still strange, since it hadn't been a problem before.

@Drake Is there an option to keep function workers working continuously once they are created?

If you're self hosting, you can increase the inactivity interval environment variable

@Drake _APP_FUNCTIONS_INACTIVE_THRESHOLD this one? what is the max value?

I would assume whatever the max integer is. I don't recall the exact value

@Drake I still get this error apearing randomly, this time in the logs is just: Preparing for start ... Starting ...

Which logs?

I get the error most often in 3 functions, the logs are from the containers associated with those functions

Weird...maybe there's something in the code that makes it slow to start

I don't think it's the code because in 90% of the time it executes in under 100ms, but it does take a while for a container to start if it's not running already so probably thats why the function gets timed out

Here is the code for one of the functions

now this is whats in the logs of one of the functions, is this normal? @Drake

and now it seems it fails constantly: Execution timed out.

Is this one the same function code you shared above?

No, it's a different function

Could you please share the code if the second one?

here

How long does it typically run for when it's successful

it's hard to tell because there is a sleep of 5 sec and that's what is shown in the dashboard on all executions, i think under a sec