Our team is working on getting back to you as soon as possible. In the meantime, we've found the following might help you get unlocked faster:

• 🧵 URGENT: Beat Service (captivating-encouragement) PostgreSQL Hostname Resolution & Service Reference Issues

• 📚 Deploy a Django App

• 🧵 Celery worker keeps crashing without deployment logs

If you find the answer from one of these, please let us know by solving the thread! Otherwise, we’ll be in touch.

Hi man,

To fix this issue of Railway marking your Celery or FastAPI logs as "errors" despite being at the INFO level, ensure all logs are explicitly routed to stdout (not stderr) by using StreamHandler(sys.stdout) and apply your logging setup in Celery using the @setup_logging.connect signal. Simplify your log format to clearly include the log level early (e.g., "%(levelname)s: %(message)s") and avoid logging complex structures like tuples or dictionaries that could confuse Railway's log parser. These changes help prevent misclassification of benign logs as errors in the Railway UI.

I'll try, thanks a lot

For future reference, our logging system does not take into account the level printed in plaintext.

The only way we parse the level is from stdout/stderr or if you do JSON logging with a level attribute, and if you are logging JSON then there is nothing you could log that could confuse the JSON parser as long as it's valid JSON.