Rank 2: Process
Many of my deployed sites, shows "Timeout
Timed out waiting for runtime.
runtime_timeout"
even that was perfectly build and working.
Votes
0
Replies
24
Participants
7
Messages
25
Rank 2: Process
Many of my deployed sites, shows "Timeout
Timed out waiting for runtime.
runtime_timeout"
even that was perfectly build and working.
also experienced this issue, after many many refreshes it started working again. is appwrite cloud stopping runtimes if they do not have traffic?
Rank 2: Process
@D5 still...
Rank 2: Process
Cloud?
It's loading
Oh, yes, throws timeout. Probably because the site is very heavy and takes a lot of time to start
Rank 2: Process
Incognito
What's the runtime that you're using?
Rank 2: Process
Node22
And framework? What's the site's size?
Rank 2: Process
NextJs
Go to the site settings and set the Resource Limits to something higher
Rank 2: Process
Yes, that's somewhat heavy, but nothing out of this world
Try this
Rank 2: Process
ok... let me try..
It's loading now, looks like the site or your config makes it run slow server side and needs either more resources or more optimization, like pre-rendering/static serving more content I think
Rank 2: Process
I am using SSR, and total size is just 220 MB, also Build takes 8-10 minutes... I have chosen 1,2 CPU but still showing same Timed out waiting for runtime. It happens with many users.
Rank 2: Process
Finally, it deployed again and now it can be accessed.
Weird. Scaling this to the team
Rank 1: Thread
I am having a very very similar issue with my site since I deployed to Appwrite Sites, I get a timed out error pretty frequently. It works sometimes, but mostly times out. Funny enough I have very similar specs as @ASHQKING. My build size is 208mb and my build duration is 8m 2s. Node 22, Next.js 16.
The same exact site is also deployed on Netlify and it deployed in 56s.
Rank 2: Process
You can try increase Resources Limit to 1CPU, 1024 MB RAM
Rank 2: Process
It works for me now.
Rank 1: Thread
I'm gonna try to up it to 2CPU, 2048 MB and and redeploy to see if it helps.