0 20 * * *
````

This runs every day at 8:00 PM.

---

## Add Workflow Steps

Each automation can contain one or more steps.

Click **Add Step** and choose the type of action you want.

---

### RCON Command

Runs a Rust RCON command.

Example:

Enter the full command and any required arguments.

---

### Delay

Pauses the workflow before moving to the next step.

The delay is entered in seconds.

Example:

equals 5 minutes.

---

### Discord Message

Sends a message to a Discord channel.

Enter the Discord channel ID and the message to send.

---

### Condition

Checks a condition before allowing the workflow to continue.

For example:

can be used to only continue maintenance when the server is empty.

---

### Server Check

Checks the current server state before continuing.

This can be used to confirm that the server or RCON connection is available.

---

### Automation

Starts another saved Atomic Automation.

This is useful for building reusable workflows.

---

## Reorder Steps

Workflow steps run from top to bottom.

Use the step controls to move actions up or down until they are in the correct order.

Example:

---

# Conditions

Conditions determine whether an automation is allowed to run.

Common conditions include:

* Server online
* Players online
* Players queued
* Players joining
* Day of the week
* Time of day

Example:

To only run when the server is empty:

To only run when 50 or more players are online:

You can choose whether:

* **ALL** conditions must pass
* **ANY** condition may pass

---

# Variables

Some automation commands and messages can use variables.

Common variables include:

Example:

AtomicBot replaces the variable with the current value when the automation runs.

---

# Run Now

Click:

**Run Now**

to start an automation immediately.

Running an automation early does **not** change its normal scheduled time.

Example:

If an automation normally runs at 8:00 PM and you manually run it at 3:00 PM:

---

# Run + Reset

Interval automations can also use:

**Run + Reset**

This runs the automation immediately and restarts the interval timer.

Example:

An automation runs every 6 hours.

If you use **Run + Reset** at 3:00 PM, the next run will be scheduled for 9:00 PM.

---

# Dry Run

Use:

**Dry Run**

to test an automation without performing its normal actions.

Dry Run is useful for checking:

* Conditions
* Target servers
* Variables
* Step order
* Command formatting

It is recommended before enabling a complicated automation.

---

# Next Run In

Each scheduled automation shows when it will run next.

Example:

The countdown updates automatically on the dashboard.

---

# Enable or Disable an Automation

An automation can be disabled without deleting it.

Disabled automations keep their settings and history but will not run automatically.

Enable it again when you are ready to use it.

---

# Pause an Automation

Use **Pause** when you temporarily want to stop an automation from running.

Unlike disabling it permanently, a paused automation can automatically become available again after the pause period ends.

Use **Resume** to remove the pause early.

---

# Duplicate an Automation

Use **Duplicate** to create a copy of an existing automation.

This is useful when creating similar schedules without rebuilding every step manually.

---

# Automation History

Click:

**History**

to view previous automation runs.

History can show:

* Run status
* Target server
* Start time
* Completion time
* Individual steps
* RCON commands
* Server responses
* Errors

Use History when troubleshooting an automation that did not behave as expected.

---

# Server Scheduler

The **Server Scheduler** tab manages Rust Console Edition's native scheduler.

Use this for simpler schedules that should be stored directly on the Rust server.

Because these schedules are stored by Rust itself, they can continue running even if AtomicBot is temporarily offline.

---

## Create a Server Schedule

Open:

**Settings → Scheduler & Automation → Server Scheduler**

Click:

**New Server Schedule**

Enter:

* Schedule name
* Schedule type
* Time
* Timezone
* Command
* Command parameters

AtomicBot automatically converts the selected local time into the UTC time required by Rust CE.

---

## Server Schedule Types

The Server Scheduler supports:

* Once
* Interval
* Daily
* Weekly
* Monthly

For complicated workflows, use **Atomic Automation** instead.

---

# Run Command Now

A native Server Scheduler entry can also be triggered manually using:

**Run Command Now**

This sends the configured command immediately without changing the existing schedule.

---

# Next Run

Managed server schedules also display:

This lets you see exactly when Rust's native scheduler is expected to run the command again.

---

# Sync Now

Use:

**Sync Now**

to rebuild the Rust CE scheduler action from the settings saved in AtomicBot.

This can be useful after changing a schedule or troubleshooting a native scheduler problem.

---

# View Live RCE Actions

Use:

**View Live RCE Actions**

to view the scheduler actions currently registered on the Rust server.

This shows the live Rust CE scheduler state.

Be careful when removing actions that were not originally created through AtomicBot.

---

# Which Scheduler Should I Use?

Use **Atomic Automation** when you need:

* Multiple commands
* Delays
* Conditions
* Player-count rules
* Discord messages
* Retry handling
* Advanced workflows
* Detailed run history

Use **Server Scheduler** when you need:

* A simple scheduled command
* A basic announcement
* A schedule stored directly on the Rust server
* A command that should continue running while AtomicBot is offline

---

# Troubleshooting

## The Schedule Shows the Wrong Time

Check:

**Settings → General Settings → Server Timezone**

Make sure the correct timezone is selected.

Do not manually compensate for UTC or daylight saving time.

---

## The Automation Did Not Run

Check:

* Is the automation enabled?
* Is it paused?
* Did all required conditions pass?
* Is the server online?
* Is RCON connected?
* Is another copy of the automation already running?

Then check **History** for more information.

---

## Run Now Did Not Change the Next Run

This is intentional.

**Run Now** executes the automation early without changing the normal schedule.

For interval automations, use **Run + Reset** if you want to restart the interval timer.

---

## A Native Server Schedule Is Not Working

Try:

**Sync Now**

Then check:

**View Live RCE Actions**

to confirm the action exists on the Rust server.

---

# Recommended Setup

For most schedules:

1. Set the correct server timezone.
2. Create the automation.
3. Choose the trigger.
4. Add the required workflow steps.
5. Add conditions if needed.
6. Use **Dry Run**.
7. Use **Run Now** for a live test.
8. Check **History**.
9. Enable the automation.

Your schedule is now ready to run automatically.