> For the complete documentation index, see [llms.txt](https://docs.paradime.io/app-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paradime.io/app-help/products/bolt/creating-schedules/command-settings/paradime-bolt-schedule-toggle-commands.md).

# Paradime Bolt Schedule Toggle Commands

## Overview

Paradime Bolt introduces a powerful feature called Schedule Toggle Commands, which allows you to dynamically control the status of a Bolt Schedule. With this functionality, you can easily pause a schedule for a specific period of time or until the next day, providing flexibility and control over your data transformation processes.

<figure><img src="/files/yONBusH9pooXELdatR19" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
**Prerequisites**

* Only UI based schedules can be pauses/unpaused using this commands
* Generate API credentials in your Paradime workspace with **Bolt schedules admin** Capabilities
* Use the generated credentials and set as [environment variables](/app-help/documentation/settings/environment-variables/bolt-schedule-env-variables.md) for Bolt Schedules

`PARADIME_API_ENDPOINT`

`PARADIME_API_SECRET`

`PARADIME_API_KEY`
{% endhint %}

### Pausing a Schedule

One of the key capabilities of Schedule Toggle Commands is the ability to pause a schedule. By issuing a pause command, you can temporarily suspend the execution of a Bolt Schedule. This is particularly useful when you need to halt the processing of data for a certain duration, such as during maintenance windows or when unexpected issues arise.

To pause a schedule, you can use the following command:

```bash
paradime bolt schedule suspend "hourly refresh"
```

{% hint style="info" %}
Use the variable `$PARADIME_SCHEDULE_NAME` to let a Bolt schedule "pause iteslf".
{% endhint %}

### Resuming a Schedule

Once a schedule is paused, you can resume its execution whenever needed. Resuming a schedule allows you to continue the data transformation process after a certain amount of time elapsed. To resume a paused schedule, you can use the following command:

```bash
paradime bolt schedule unsuspend "hourly refresh"
```

{% hint style="success" %}
Normally, the `suspend` and `unsuspend` commands will be part of two separate schedules.

For example, you can have one schedule that runs the `suspend` command at a specific time or interval to pause the execution. This schedule can be configured to run at the desired frequency, such as daily or weekly, depending on your requirements.

On the other hand, you can have another schedule that runs the `unsuspend` command at a different time or interval to resume the execution of the suspended Bolt Schedule. This schedule can be set up to run at the appropriate time when you want the data transformation process to resume.
{% endhint %}

***

Now, let's learn how to configure the [Trigger Types](/app-help/documentation/bolt/creating-schedules/trigger-types.md) of a Bolt Schedule.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.paradime.io/app-help/products/bolt/creating-schedules/command-settings/paradime-bolt-schedule-toggle-commands.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.