Keep Serverless turned on, then deploy from source using the command palette: press Ctrl+K (Cmd+K on Mac), then select Deploy latest commit.

I followed your instructions and selected Deploy latest commit, but it still failed with exactly the same error. Serverless is ON, and the build succeeds, but deployment never starts. Could someone please check the service on your end? I’ve tried everything suggested so far and it still isn’t working.

Try turning it off, deploy latest commit, turn it back on, then deploy again.

Both "dating-sim-bot" and "telegram-bot-api" have Serverless turned ON. I also tried deploying the latest commit. The bot briefly showed Online, then crashed after 1–2 seconds. The Telegram API service still fails with the Free-plan Serverless error, and Railway isn't showing me any useful logs. What should I do next?

Just a sanity check, the latest deployment's error log was that serverless must be on?

Yes, it still shows that error even though Serverless is ON for both services. I tried deploying again, but it didn't work.

Are you sure you deployed the latest commit through the command palette? (Select the service, then press Cmd/Ctrl + K, then select deploy latest commit)

I'm using mobile, so I selected Redeploy from the latest deployment's menu. The service is Online now, and the bot is responding again. However, I'm not sure if this deployed the latest commit or fixed the sleeping issue permanently.

Just FYI, redeploying from the 3 dot menu is not the same as performing the actions I described above. But good to know it’s working now.

Nice, glad it's back up!

About your questions: Redeploy from the 3 dot menu just reruns that same deployment, same commit and same settings it was created with. So it's probably not your latest commit. Open the active deployment and compare the commit hash with the latest one on GitHub. If it's older, just push a new commit to the branch and Railway will deploy it automatically (easiest way from mobile). Or open railway.com in desktop mode on your phone and do Ctrl+K > Deploy latest commit.

And yes it should stay working. As long as Serverless stays on and you deploy new commits instead of redeploying old ones, you shouldn't see that error again.

About sleeping, Railway puts the service to sleep after ~5-10 min with no outgoing traffic. If your bot uses polling it's calling Telegram all the time, so it won't really sleep. If it uses webhooks it'll sleep and wake up on the next message, the first reply might just be a bit slow.

Also, do you actually need the telegram-bot-api service? If the bot is replying now it's probably talking to Telegram directly, so you might not need it and can save your free plan resources.

If it starts crashing again check the deploy logs. If you see "409 Conflict" it means another copy of the bot is running with the same token.