Schedules

Schedules define when your processes run automatically. RPA Watch syncs schedules from your connected RPA tools, giving you visibility into the automation calendar.

Schedule List

Navigate to Schedules in the sidebar to see all schedules in the current account. The list shows:

- Name — Schedule display name

- Process — Which process this schedule triggers (if linked)

- Cron Expression — When it runs (e.g., 0 8 * * 1-5 for weekdays at 8 AM)

- Timezone — Which timezone the schedule uses

- Status — Active or Inactive

- RPA Tool — Robomotion or UiPath

Understanding Cron Expressions

Schedules use cron expressions to define their timing. Common patterns:

The format is: minute hour day-of-month month day-of-week

Timezone Handling

Each schedule has an associated timezone. The cron expression is evaluated in that timezone:

- Robomotion schedules include the timezone from the Robomotion API

- UiPath schedules include the TimeZoneId from the Orchestrator

RPA Watch displays the timezone alongside the cron expression so you know exactly when the schedule fires.

Active vs. Inactive Schedules

| State | Description |

|-------|-------------|

| Active | The schedule is enabled and the process will run at the specified times |

| Inactive | The schedule is disabled — no automatic executions |

Schedule status is synced from your RPA tool. Activating or deactivating a schedule must be done in the RPA tool itself — RPA Watch provides read-only visibility.

Schedule-Process Linking

Schedules reference processes by their external ID:

- Robomotion: Uses the published flow ID or flow ID

- UiPath: Uses the release key

If the referenced process exists in RPA Watch, the schedule shows a clickable link to the process detail page. If the process hasn't been synced yet, the schedule displays the external reference ID.

Syncing Schedules

Schedules are synced as part of the [automatic sync](/docs/automatic-sync) process:

- Synced every 15 minutes

- New schedules are created, existing ones updated

- Schedules removed from the RPA tool are soft-deleted

- Manual sync also includes schedules

Using Schedules for Monitoring

Schedules help you answer operational questions:

- "Is the daily invoice process scheduled?" — Check if the process has an active schedule

- "Why didn't the process run?" — If the schedule is inactive, the process won't trigger

- "When does it run next?" — Read the cron expression with timezone

Combine schedule information with [job history](/docs/runs-and-run-history) to verify that scheduled processes are actually executing on time.

Missed Schedule Alerts

When [alerts are enabled](/docs/alerts) for an account, RPA Watch automatically detects missed schedules:

- The system checks every 15 minutes for processes that should have run but didn't

- A configurable grace period (5–120 minutes) allows for normal startup delays before triggering an alert

- A cooldown period (30–1440 minutes) prevents repeated notifications for the same schedule

- Schedules running more frequently than every 5 minutes are excluded to avoid noise

- Alerts are sent via email to the process owner and all assigned members

- Alerts auto-resolve when the expected run eventually completes

See [Alerts](/docs/alerts) for full details on configuring and managing alerts.