Error: Environment variable DATABASE_URL not set – Unresolved per‑project timezone for scheduled tasks

Environment variable DATABASE_URL not set

Deploying a Railway project without the DATABASE_URL environment variable triggers the CLI to abort with the explicit error message:

Environment variable DATABASE_URL not set

While the container runtime honors a TZ variable, scheduled tasks continue to run in UTC and the platform provides no documented option to override this per project or per task.

The unresolved design decision is whether Railway will expose a per‑project timezone configuration for scheduled tasks, and how such a setting would interact with database timestamps that are also stored in UTC.

Specifically:

• Does Railway currently support setting a per‑project timezone for scheduled tasks?
• If not, what is the recommended approach to align scheduled tasks with a local time zone?
• Will future releases add a timezone override for scheduled tasks?