Missing runtime logs for Cron runs (“No logs found for this filter”) despite confirmed execution
ayodukale
HOBBYOP

a month ago

What’s happening

What I tried

  1. Observability / Log Explorer

    • Filtered to the specific service (@service:"Daily-Ladder")

    • Expanded time windows (Last day / 7 days)

    • Still shows “No logs found for this filter” for today.

  2. Railway CLI

    • Ran railway logs --service Daily-Ladder --tail 200 → returns no output

    • Listed deployments and attempted fetching logs by deployment ID → logs empty.

    • Confirmed the runs are occurring (cron executions complete).

  3. Reruns / redeploy

    • Manually triggered the cron run 3 times

    • Performed a rebuild/redeploy and ran again afterward

    • Still no logs for today.

Additional observation

  • Other services in the same project do show logs, and the log explorer shows activity (e.g., database checkpoints / other services), but this service has no runtime logs ingested today.

I’ve seen similar Railway Station threads where log ingestion disruptions were acknowledged and sometimes resolved after redeploy but in this case redeploy + reruns still produce no logs for today.

Appreciate any help you may be able to provide.

Solved

6 Replies

sam-a
EMPLOYEE

a month ago

Hey, we identified an issue with the log forwarding service on the host where your cron job runs. We've restarted that service and logs should now be flowing correctly.

Your next cron run (or a manual trigger) should show logs as expected. Let us know if you're still not seeing them after that.


Status changed to Awaiting User Response Railway about 1 month ago


ayodukale
HOBBYOP

a month ago

Thank you!


Status changed to Awaiting Railway Response Railway about 1 month ago


Status changed to Solved ayodukale about 1 month ago


ayodukale
HOBBYOP

a month ago

Okay I triggered another deployment today after making updates and the issue is resurfacing.
I am unable to get logs on my latest run... this is making it a bit challenging to debug issues.. would appreciate any help you can provide to resolve this persistent issue


Status changed to Awaiting Railway Response Railway about 1 month ago


sam-a
EMPLOYEE

a month ago

Did you see logs after the earlier message we sent and then stop seeing again or did you never see logs?


Status changed to Awaiting User Response Railway about 1 month ago


ayodukale
HOBBYOP

a month ago

I saw it on the run you triggered on your end but after that, nothing so it seems I'm unable to trigger it on my end


Status changed to Awaiting Railway Response Railway about 1 month ago


a month ago

It looks like the last issue was a runtime error and did provide logs. Are you still encountering this issue?


Status changed to Awaiting User Response Railway about 1 month ago


Railway
BOT

25 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 25 days ago


Loading...