---
title: Automations
description: Run a cloud agent on a schedule with saved instructions. Create automations by talking to the Railway Agent, review each run, and get notified on failures.
---
Automations are available through [Priority Boarding](/platform/priority-boarding), in the Railway Agent Dashboard. Breaking changes may occur.

An automation runs an agent on a schedule. You write the instructions once, pick when they run, and Railway starts a fresh [cloud agent](/cloud-agents) in your project at the scheduled time.

Use one for recurring work, like summarizing yesterday's errors every morning, checking dependencies for updates each week or making automated decisions based on data from analytics.

## Create an automation

You set up an automation by chatting with the agent.

1. Open your project and click **Automations** in the sidebar.
2. Click **New automation**.
3. Tell the agent what the automation should do and how often.
4. Check the name, instructions, and schedule it proposes, then confirm.

The agent then offers to run the task once so you can check the result before the schedule takes over.

## Schedules

Schedules are cron expressions in UTC. Each one runs at most once an hour, and an automation can have more than one schedule. For example, `0 9 * * 1` runs every Monday at 09:00 UTC.

You don't need to write cron yourself. Tell the agent when you want the automation to run, and it shows the times in your timezone and in UTC before saving.

## Manage an automation

Open an automation from the **Automations** page:

- Click **Run now** to start a run right away, even when the automation is paused.
- Toggle **Enabled** to pause or resume the schedule.
- Click the **more actions** menu to **Edit** or **Delete** the automation.

## Runs

Clicking into an automation shows you all previous runs. Click a run to open its chat and see what the agent did. You can respond in the same chat with follow ups if you have any.

When a run fails, Railway notifies you by email and in the dashboard. There are no retries for failed runs.

A run's chat is deleted 7 days after the run finishes. The run stays in the list, marked **Chat expired**.

## Who can see your automations

Only the automation creator can see and manage the automations, including their runs and chats. Teammates and workspace admins can't see them. Runs act with the permissions of the creator in the project.

Team-based automations are coming soon.

## Use automations from an AI assistant

Your AI assistant can create, run, and manage your automations through the [Railway MCP server](/ai/mcp-server).

## Billing and limits

Runs use your [default model](/ai/bring-your-own-models#2-choose-a-default-model). Each run starts a new cloud agent and is billed like a [cloud agent task](/cloud-agents/tasks#billing).

- Each schedule runs at most once an hour.
- Instructions can be up to 32,000 characters.
- Each run counts toward your [task dispatch limit](/cloud-agents/tasks#limits).
- Run chats are deleted 7 days after the run finishes.