Migration Guide

Migrate from Railway Cron

Schedule jobs independently of your deployment. Proper alerting on failure.

Step by step

1

Find your Railway cron services

In your Railway project, identify services configured to run on a cron schedule.

2

Expose logic as HTTP endpoints

Add HTTP routes to your Railway web service for each cron task.

// Express
app.post('/cron/task', verifySecret, async (req, res) => {
  await runTask();
  res.json({ ok: true });
});
3

Create JustRun jobs

For each Railway cron service, create a JustRun job with the same schedule and your Railway web service URL.

4

Add authentication

Set a shared secret header in JustRun job settings and validate it in your route handler.

5

Disable Railway cron services

Once verified, delete or disable the Railway cron services. Keep Railway for your web services and databases.

Common questions

Why decouple from Railway's built-in cron?

Railway's cron has no failure alerting and no retry policies. JustRun adds AI diagnostics, escalation policies, and a CLI — and works regardless of your deployment platform.

Will this affect my Railway bill?

Removing cron services reduces Railway compute usage. JustRun costs $3–7/mo and doesn't spin up Railway instances.

Ready to migrate?

Free to start. Import in under 2 minutes.

Start Free