can you show a screenshot of the expanded logs?

also what logger library you are using and the formatting involved with that

update: someone else had the same issue and with their help i was able to reproduce, if your issue is the exact same as theirs it means you are using json structured logging and railway is not picking up your message attribute, but funny enough it will pick up a msg attribute and display that attribute as your message.

I will bring this up to the team.

I'm using nestjs + wintson with the following formatting

format.combine(format.errors({ stack: true }), format.timestamp(), format.json(), PIIFormat())

and I can confirm, on the legacy runtime, the message that was showing on the log line was the one with the message key in json format. Since I'm mostly relying on newrelic for all my logs anyway, I'm not gonna change anything on my logger, will wait to hear from you/team back about that

I'm sure this would be a super easy fix

yep, will take a look when I can

haha sorry not for you, I mean for the team, you aren't doing anything wrong

the team is hands on keyboard to fix the logging issue

update: one half of this problem has been fixed, structured logs with a message attribute will not be blank anymore, the missing logs are still being worked on

Sweet! I can confirm, it's showing again for me

will update further when I have more information about the outright missing logs

update: the missing logs are fixed, but theres a new issue that arose with the possibility of them being not shown in the correct order

sorry for the late reply, but all known logging issues on the v2 runtime have been fixed