# Schedule Configurations After creating a Bolt Schedule, you can view and modify it to suit your evolving needs. This section covers how to view and edit Bolt Schedules via the UI and highlights essential actions for managing your schedules. ### Table of Contents * [Viewing Bolt Schedule List](#viewing-bolt-schedule-list) * [Modifying Existing Schedules](#modifying-existing-schedules) * [Managing Scheduled Runs](#managing-scheduled-runs) * [Trigger a Manual Run](#trigger-a-run-manually) * [Cancel a Running Schedule](#cancel-running-schedule) * [Pause a Schedule](#pause-a-schedule) * [View a Schedule’s YAML Code](#utilize-a-schedules-yaml-code) * [“Defer to Production” Configuration](#defer-to-production-configuration) ### Viewing Bolt Schedule List The Bolt home page provides a summarized list of all the schedules configured in your Paradime workspace. {% hint style="info" %} Bolt Schedules created through the `paradime_schedules.yml` file are available in the Bolt UI and can also be reconfigured there. However, schedules created directly in the Bolt UI are not version-controlled and will not appear in the `paradime_schedules.yml` file. {% endhint %} Here you can view preview details of each schedule, including: | Column | Description | Example Value(s) | | --------------------------- | --------------------------------------------------------------------------------- | --------------------------------------------------- | | Name | Name of the schedule | `"production run"` | | Status | Current run status of the schedule | `Success`, `Error`, `No Runs`, `Running` | | Owner | The owner of the schedule (if configured) | `john@acme.com` | | Cron Description | The time of day (UTC time) that the schedule runs, defined by cron configuration. | `OFF`, `At 00:00, every day (UTC)` | | Cron Configuration | The cron syntax of the scheduled run. | `OFF`, `@daily`, `0 8 * * *` | | Last Run | Date and time of when the schedule was last triggered | `October 31, 2024 at 5:00 PM PDT` | | Next Run | Date and time the scheduler will trigger next | `November 1, 2024 at 5:00 PM PDT` | | Trigger Type | How your schedule is triggered | `On Schedule`, `On run completion,` | | On completion Configuration | Details on how your `On Run Completion` is configured (If applicable) | `schedule medium in workspace max on status passed` | Use this list to view all schedule names parsed, including any [schedules configured as code](https://docs.paradime.io/app-help/documentation/bolt/creating-schedules/schedules-as-code). ### Modifying Existing Schedules 1. **Navigate to the Bolt UI** and select the schedule you wish to edit. 2. **Click “Edit”** to access the schedule's configuration settings. 3. Update any necessary schedule parameters, including **Schedule Type**, **Commands**, **Trigger Type**, and **Notifications**. 4. **Deploy your changes** to save the updated configuration. {% hint style="info" %} Alternatively, you can modify schedules directly in the `paradime_schedules.yml` file within your dbt™ project. For details, refer to [View a Schedule’s YAML Code](#utilize-a-schedules-yaml-code) {% endhint %} {% @arcade/embed flowId="B3FIRpl2KthtrXNOh2r9" url="" %} ### Managing Scheduled Runs Bolt offers four trigger types for schedules: #### Trigger a manual run In addition to automatic executions, you can trigger manual runs for Bolt Schedules as needed: 1. **Navigate to the Bolt UI** and select the specific schedule. 2. Click the **Run** button in the top right corner to initiate a new run. {% @arcade/embed flowId="vT8iGFpcS9m5uTsDKBHU" url="" %} #### Cancel running schedule While the schedule is active, click the **Cancel** button next to the currently running schedule. {% @arcade/embed flowId="qEfFM6voKozWQfM256lj" url="" %} #### Pause a Schedule To temporarily disable a schedule: 1. **Click on the schedule name** to view its details. 2. Click **Edit** to begin modifying the schedule. 3. At the top of the editor, toggle the **switch off** to pause the schedule. {% @arcade/embed flowId="CLw0UVgsvmN1EAq94MMv" url="" %} *** ### Understanding Schedule States Bolt schedules can be either **Active** or **Archived**. Active schedules can be found in the main schedule list, while archived schedules are accessible via the "Active Schedules" dropdown menu.
#### **About Archived Schedules** A schedule becomes archived when: * It is removed from the `paradime_schedules.yml` file * It is deleted through the Bolt User Interface * Its name is changed (the schedule with the old name becomes archived) To restore an archived schedule: * **Schedule created via UI**: Access the archived schedule, click Edit, and deploy again * **Schedules created via** [**code**](https://docs.paradime.io/app-help/documentation/bolt/creating-schedules/schedules-as-code): Add the schedule back to `paradime_schedules.yml` using its original name *** ### View a Schedule's YAML, Airflow, and Python code Paradime offers multiple ways to trigger and manage Bolt Schedules. You can choose the method that best suits your workflow, from version-controlled **YAML** configurations to orchestration with **Airflow** or integration with custom scripts using the **Python SDK**. To access the code for each method: 1. **Click on the Bolt schedule name** to view the schedule details. 2. Click **Edit**. 3. Click **“\ Code”** to view the YAML, Airflow, and Python code options. Use the tabs below to explore specific code examples for each option: {% @arcade/embed flowId="3HyIQ6JrNlBBrjGOJkzy" url="" %} *** ### "Defer to Production" Configuration To use a production schedule during development in the IDE and [defer to the production](https://docs.paradime.io/app-help/concepts/paradime-fundamentals/dbt-tm-defer-to-production) schema for upstream tables, select the desired schedule name from the dropdown menu. {% hint style="info" %} Learn more about how Defer to Production works in our learning guide, [Using --defer in Parading](https://docs.paradime.io/app-help/concepts/paradime-fundamentals/dbt-tm-defer-to-production) {% endhint %} {% @arcade/embed flowId="Dr7emT3fbhyBW98klIeq" url="" %}