---
title: "Schedule a batch transcription task to run automatically"
description: "Set a weekly run time for a batch transcription task, read the Next run and Trigger columns, and understand what happens when a schedule is disabled or skipped"
canonical_url: "https://docs.ardge.com/en/knowledge/scribestt/schedule-batch-runs"
---
# Schedule a batch transcription task to run automatically

> Set a weekly run time for a batch transcription task, read the Next run and Trigger columns, and understand what happens when a schedule is disabled or skipped

## Overview

Besides triggering a batch transcription task by hand, you can schedule it: the system creates a run automatically on the days and time you choose each week. When recordings keep accumulating on a NAS, a schedule saves you triggering it every time.

This article covers adding a schedule to an existing task, how times are converted, and what happens when a schedule is disabled or skipped.

## What you'll learn

- Set a fixed weekly run time for a batch transcription task
- Read the **Next run** and **Trigger** columns
- Understand what the system does when a schedule is disabled, missed, or skipped

**Estimated time: about 5 minutes**

## Applies to

- ARX OS 1.0 and later
- ScribeSTT 1.3.0 and later

## Before you begin

- The batch transcription task exists — see [Connect a NAS data source and create a batch transcription task](https://docs.ardge.com/en/knowledge/scribestt/nas-batch-transcription)
- That task has no run in progress. A task with a run in progress can't be edited, and trying reports "The task has a run in progress and can't be modified"

## Step 1: Open the task's schedule settings

1. Go to the **Tasks** page
2. On the task's row, click the more icon at the far right of the **Actions** column and choose **Edit**
3. Find the **Schedule** field in the **Edit task** dialog
4. Turn on the toggle to the right of **Schedule**

The day and time pickers go from disabled to available, defaulting to every day at `00:00`.

## Step 2: Pick the days and time

1. Select the days to run in the day picker — several are allowed
2. Click the time picker and choose the hour in the left column and the minutes in the right
3. Click **Save**

<warning>

**At least one day is required:**

With the schedule on but no day selected, submitting shows "Select at least one day".

</warning>

The page shows "Task updated", and the task row's **Next run** column shows the next moment matching the schedule.

<tip>

**Times are entered in your browser's time zone:**

The system stores and evaluates schedule times in UTC; what you enter and see on screen is converted to your browser's time zone. Crossing midnight shifts the day accordingly — Monday 07:00 in UTC+8 is Sunday 23:00 in UTC. Viewing the same task from browsers in different time zones shows the days and times in each one's own zone.

</tip>

## Disabling a schedule and missed times

Once set, a schedule can't be cleared — only disabled: turn the **Schedule** toggle off in the **Edit task** dialog and save. Turning it off keeps the days and time in the form, so turning it back on restores what you had.

Times missed while it was disabled are never made up. Once you re-enable it, the system calculates the next matching moment from that point on — it never goes back to fill in the ones it skipped.

## When a run is already in progress at the scheduled time

One task can have only one run in progress at a time. If the scheduled time arrives while a run is still going, that schedule is skipped — the system doesn't queue it, and it doesn't run it once the current one finishes. It simply waits for the next matching moment.

When the source folder holds a lot of files and one run may take longer than the interval between schedules, set a more generous interval, so most scheduled times aren't skipped because the previous run is still going.

## Reading the Next run column

The **Next run** column in the **Tasks** list shows "the next moment matching the schedule settings", calculated live on every query.

It shows `-` in three cases:

- The task has no schedule
- The schedule is disabled
- The schedule's conditions can never be satisfied

The column doesn't guarantee a run will be created then. If the task has a run in progress when that moment arrives, it's still skipped.

<note>

**How often schedules are checked:**

The system polls for due schedules at a fixed interval, 30 seconds by default. A run's creation time can therefore be tens of seconds later than the time you set.

</note>

## Reading the Trigger column

The **Trigger** column in **Run history** has only two values:

<table>
<thead>
  <tr>
    <th>
      Value
    </th>
    
    <th>
      What it means
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Scheduled
      </strong>
    </td>
    
    <td>
      Created automatically by this system's schedule at the set time
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Manual
      </strong>
    </td>
    
    <td>
      Everything else — <strong>
        Trigger task
      </strong>
      
       in the web interface, the CLI, and calls from external programs
    </td>
  </tr>
</tbody>
</table>

Those three manual sources can't be told apart in this column. To work out who triggered a run, cross-reference the run's creation time with your activity records for that period.

## Related articles

- [Connect a NAS data source and create a batch transcription task](https://docs.ardge.com/en/knowledge/scribestt/nas-batch-transcription)
- [Why are some files marked as skipped?](https://docs.ardge.com/en/knowledge/scribestt/skipped-files)


## Sitemap

See the full [sitemap](https://docs.ardge.com/sitemap.md) for all pages.