a year ago
I just migrated my primary, worker, redis and postgres all to Southeast Asia region under settings. Not sure if it's due to that, now when I try to run my workflow, it gets stuck.
33 Replies
I am also getting an email from Railway saying I ran out of memory - which shouldnt be the case since I just upgraded to Hobby plan with 8GB RAM
a year ago
Have you redeployed every service since upgrading to Hobby? your limits are only bumped after a clean re-deploy.
a year ago
Oh, you're talking about n8n. I'm afraid this has nothing to do with the Railway upgrade.
Try enabling executions queue mode. This should and prevent non-malfunctioning executions from stalling.
testuser123
Oh, you're talking about n8n. I'm afraid this has nothing to do with the Railway upgrade. Try enabling executions queue mode. This should and prevent non-malfunctioning executions from stalling.
a year ago
It could have something to do with Railway if they haven't redeployed since upgrading to Hobby.
a year ago
All 4 services?
a year ago
Not restart, a re-deploy?
a year ago
Then I will let the community involve themselves in this thread to help you.
a year ago
have you done this?
I took a break after sending out my last message, and went I came back and tried executing it works fine
maybe the server just needed time to reflect that I am on 8GB RAM and not 500MB?
Quick question: Does it make sense to deploy my service instances in Singapore (Southeast Asia) if I am based in Malaysia?
I have just changed from the default US to Singapore instead for all my services
Does it make things faster by any chance? What does it implicate by deploying them nearer to where I'm at?
a year ago
The servers all have similar capacity and hardware. The only measurable difference will be latency.
a year ago
Your latency to Singapore will be much less than to the US. You should be using Singapore
a year ago
!s
Status changed to Solved adam • 11 months ago