2 months ago
It worked fine before a deploy. on note project looks good but on python looks weird. doesn't format them well. What happeend here?
Attachments
25 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 months ago
2 months ago
this is how on my node project looks like and it was looking on python too but stopped after changing branches after a merge
Attachments
2 months ago
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
2 months ago
That's logs attributes, nothing to do with python-json-logger because what truncated there is the attributes not the log data/message
silviust7
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
2 months ago
Might be bug on the web dashboard, can you try force refresh the page?
silviust7
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
2 months ago
Does the log data/message visible on the mobile dashboard?
mayori
Does the log data/message visible on the mobile dashboard?
2 months ago
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
Attachments
2 months ago
Since the issue came after a deploy, can you try redeploy or deploy latest commit and see if the issue persist or not?
silviust7
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  
2 months ago
What browser you're using?
mayori
What browser you're using?
2 months ago
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"
}
Attachments
2 months ago
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?
coppa
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?
2 months ago
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
mayori
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
2 months ago
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")
coppa
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") ```
2 months ago
Attachments
2 months ago
I've escalate this issue to the team, They're investigating on this issue
2 months ago
I have the same issue
mayori
This issue is fixed, Can you guys check your logs?
2 months ago
Thank you, everything is displaying correctly now
2 months ago
I still have an issue: I can see all my logs but when I search @level:warn or @level:error , nothing is displayed...
2 months ago
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
guarouba
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
2 months ago
Can you share the screenshots here?
2 months ago
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
Attachments
guarouba
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`  
2 months ago
Team is investigating on this! I'll post update here
guarouba
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`  
2 months ago
Log level filtering issue is fixed, Can you check?
Status changed to Solved mayori • about 2 months ago