I’m deploying a Python Telegram bot (Aiogram 3, polling mode) from GitHub. Recently deployments for the service show “Deployment failed” (or get stuck on “Creating containers…”), but there are no useful logs in both Deployment logs and Runtime logs (almost empty).

What I expect

Deployment should start the container and show runtime logs like “bot started / polling started”.

What happens instead

• Deployment UI shows failed / stuck at “Creating containers…”

• Logs are empty (no traceback, no Python output)

• Previous successful deploys exist (core8_1.py deployed successfully earlier, grammar_feature.py deploy fails / stuck)

Context / stack

• Python app, Telegram bot (Aiogram 3)

• Runs in polling (does not expose HTTP port)

• Uses Railway Volume mounted at /data (app creates /data folder on start)

• Start command (expected): python core8_1.py

• Code is built from GitHub deployment

Troubleshooting already done

• Checked code for syntax errors; current version compiles locally (no SyntaxError).

• Re-deployed multiple times; behavior persists.

• Checked both Deployment logs and Runtime logs: still empty.

• No secrets/tokens are printed in logs.

Request

Could you please check why the container fails / gets stuck without producing logs?
Maybe the process exits immediately, or there is an internal platform issue (container creation, volume mount, runtime logging).
If possible, please provide internal container startup logs / exit reason (OOM, crash loop, missing entrypoint, volume mount error, healthcheck issue, etc.).

Project/service: proyecto_bot (production)