# Cron & Jobs Tab

## Member Cron & Jobs

Use **Cron & Jobs** to see scheduled work and recent server tasks for a member. It helps you confirm whether backups, discovery runs, refreshes, and other actions are queued, running, completed, or failed.

### What it is for

<div id="bkmrk-area-what-you-use-it-1"><div><table><thead><tr><th>Area</th><th>What you use it for</th></tr></thead><tbody><tr><td>**Schedules**</td><td>View and manage recurring jobs for the selected member.</td></tr><tr><td>**Recent jobs**</td><td>Check the latest actions sent to the member.</td></tr><tr><td>**Run now**</td><td>Trigger a supported scheduled task immediately when available.</td></tr><tr><td>**History**</td><td>See whether work completed or needs attention.</td></tr></tbody></table>

</div></div>Times are shown in the product interface for easy reading. When you are coordinating with logs or support, include the member name and the job time shown in the UI.

### Free and Pro

<div id="bkmrk-feature-community-pr-5"><div><table><thead><tr><th>Feature</th><th>Community</th><th>Pro</th></tr></thead><tbody><tr><td>View recent jobs and outcomes</td><td>Included</td><td>Included</td></tr><tr><td>See existing schedules</td><td>Included</td><td>Included</td></tr><tr><td>Create recurring schedules</td><td>Upgrade required</td><td>Included</td></tr><tr><td>Edit, pause, resume, or delete schedules</td><td>Upgrade required</td><td>Included</td></tr><tr><td>Run scheduled jobs on demand</td><td>Upgrade required</td><td>Included</td></tr><tr><td>Use backup and discovery automation</td><td>Upgrade required</td><td>Included</td></tr></tbody></table>

</div></div>Pro is where Cron &amp; Jobs becomes automation instead of just visibility. It is intended for teams that want regular backups, routine discovery refreshes, and repeatable maintenance without manual checklists.

### Using recent jobs

Open **Cron &amp; Jobs** and look at the recent job list.

Each job usually shows:

- What action was requested.
- The current state.
- When it started or finished.
- The member that handled it.
- Any visible failure reason.

If a job fails, use the failure message to decide the next step. Common causes are stale agent heartbeat, missing storage, low disk space, incompatible service type, or a feature that requires Pro.

### Using schedules

Schedules are useful for repeated operational work.

To create a schedule on Pro:

1. Open **Cron &amp; Jobs**.
2. Choose **Add schedule**.
3. Pick the job type.
4. Set the timing.
5. Confirm the target and save.

Use schedules for routine backups and refresh tasks. Avoid scheduling risky changes unless the result is easy to verify and recover from.

##### Good operating habits

- Check recent jobs after starting a backup, restore, transfer, or discovery run.
- Keep schedules simple and clearly named.
- Pause schedules during major migrations if they could interfere.
- Use Pro schedules for regular backup and discovery coverage.