24 days ago
Environment: Railway CLI 5.30.1 on macOS arm64.
We used the official read-only runtime logs command scoped by an exact deployment ID plus --since and --until for a four-minute UTC window. The command returned exit 0 with zero log lines and empty stdout/stderr. One adjacent four-minute window produced the same result. We did not use an unbounded search or a --lines cap.
Could Railway please:
- Provide a private channel where we can share the exact deployment ID and UTC timestamps, then provide the official stdout/stderr export or confirm that the logs have passed their retention period.
- Explain whether this query can be paginated or truncated, and what metadata ties an export to the requested deployment.
- If export is unavailable, identify a platform-supported authenticated read-only proof path.
- Treat this separately from Railway CLI issue #1029: this request concerns runtime-log retention/export, not remote command execution.
No customer data, raw logs, credentials, project identifiers, service identifiers, or deployment identifiers are included in this public post.
1 Replies
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
On the Hobby plan, runtime logs are retained for 7 days. A deployment-scoped query outside that window returns zero lines with exit 0 - the API returns an empty result, not an error.
The CLI applies an implicit 500-line cap per historical fetch (when using --since/--until), with no pagination. The query is a single request to the deploymentLogs GraphQL endpoint, and the result includes the deployment ID in the query scope, so each response is inherently tied to the requested deployment. To retrieve more than 500 lines, narrow the --since/--until window and issue multiple calls.
The two authenticated, deployment-scoped read paths are the CLI (railway logs <DEPLOYMENT_ID> --since ... --until ...) and the public GraphQL API (deploymentLogs query with startDate/endDate variables). Both return the same data as the dashboard's deploy logs tab. There is no separate export endpoint beyond these.
For retention beyond 7 days, forward stdout to a third-party provider using a log forwarder per the observability guide, or upgrade to Pro for 30-day retention.
Status changed to Awaiting User Response Railway • 24 days ago
Status changed to Solved mykal • 24 days ago