this is how on my node project looks like and it was looking on python too but stopped after changing branches after a merge

Have you installed python-json-logger in your project?

using Python's standard library logging. it was looking fine before a deploy but now is not. on mobile app looks fine showing the message above though so i am thinking is an issue on Railway side

Install it with pip install python-json-logger. This should be added to your requirements.txt and also imported into your code before redeploying.

That's logs attributes, nothing to do with python-json-logger because what truncated there is the attributes not the log data/message

Might be bug on the web dashboard, can you try force refresh the page?

Looks like a structlog issue. If it's structlog, worth checking EventRenamer target. It should be returning a message instead of event_name

Does the log data/message visible on the mobile dashboard?

Ensure these checks in your service logs under your project dashboard

.

Verify all checks here

seems an issue on railway. when i look from a service -> deployments -> view logs it shows this error but when i look from logs and select the service i see the logs fine. Refresh did not do anything

Can you show your Logs View Options?

Since the issue came after a deploy, can you try redeploy or deploy latest commit and see if the issue persist or not?

What browser you're using?

I am using safari (Version 26.6 (21624.4.5.11.5)), i had deployed and redeployed multiple times trying to fix it and in vain

Structured JSON logs from Python (logging.StreamHandler → stdout) show "message": "" in the log explorer / raw envelope. The same JSON field is present on stdout.

Working: Our Node service on the same project logs console.log(JSON.stringify({message: "..."})) and Railway shows the message correctly.

{

  "message": "",

  "severity": "info",

  "attributes": {

    "level": "info",

    "event_name": "api.cache.miss",

    "logger": "api",

    "ts": "2026-08-13T14:41:54.830Z",

    "type": "market_tags",

    "slug": "ethereum-above-1910-on-august-13-2026-12pm-et"

  },

  "tags": {

    "project": "3534901f-2f6f-4a72-979c-c6ec6d376f99",

    "environment": "09ebf625-906d-44d3-b2ca-da2164c55cb3",

    "service": "a0d77487-4766-4ce1-9a09-c0c07165bd3b",

    "deployment": "4046d530-827c-4e97-a805-81093c3c886f",

    "replica": "60b6e2b0-4fe6-43ca-9ba9-93a6b4b1f372"

  },

  "timestamp": "2026-08-13T14:41:54.881129236Z"

}

I've run into this problem too. It's clearly an update from Railway. They've released another Ai-slop

I wonder, does this mean that all the logs from the period after the update are now lost for good, or will they be restored?

I'm still trying to reproduce the issue but haven't found anything, but it seems like this issue only occurs on Service Deploy Logs, You should still able to see it through Observability Logs

Run this test python script on Railway, it reproduces the problem

import json

def log(level: str, message: str, logger: str = "test", **kwargs) -> None:
    print(json.dumps({**kwargs, "message": message, "level": level, "logger": logger}, ensure_ascii=False))

log("info", "test info message", user_id=42, action="login")
log("warning", "test warning message", retries=3)
log("error", "test error message", error_code="E500")

I've escalate this issue to the team, They're investigating on this issue

I have the same issue

This issue is fixed, Can you guys check your logs?

Thank you, everything is displaying correctly now

I still have an issue: I can see all my logs but when I search @level:warn or @level:error , nothing is displayed...

Have you try force refresh the page?

Yes and I cannot filter my logs using the @level tag anymore .. Using @level:info shows all logs including error logs. And @level:error shows nothing

Can you share the screenshots here?

I hide the data column but you can see that without the level tag there are errors that are not shown when using @level:error

Team is investigating on this! I'll post update here