> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.method.security/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.method.security/_mcp/server.

# Run a Task

> Run a Task on demand or schedule it to run on a recurring cadence

Run a [Task](/platform/core-platform/automations) once on demand, or set up a schedule to run it on a recurring cadence.

---

## Open the run form

There are two ways to start a Task Run.

### From the Task page

Open the Automator app, click into the Task you want to run, and look in the top-right corner of the Task page.

![Task detail page with Overview tab selected and Run and New Schedule buttons highlighted in the top-right corner](/_fern-files/_img/491984932174e654eec2e75b9017350dc969b64f4a0a7c6892b255fbe7394835.webp)

* Click **Run** to launch a one-time Task Run on demand.
* Click **New Schedule** to set up a recurring Task Run.

### From the quick-action menu

Click the **lightning bolt** icon in the left sidebar to open the **Start something new** menu, then select **Run an Automation**.

![Start something new panel with Run an Automation highlighted](/_fern-files/_img/b3adc268dffe3874ac9ebfc718927b1987f737a156195e265fdb8360d827feba.webp)

A **Select Task** picker opens. Search for and pick the Task you want to run.

![Select Task picker showing search results for Bastion EASM Flow Tasks](/_fern-files/_img/3bed7d92a6f413422a21035cb53e5cb06c3f8ecc5f865d295087f92af63bdd91.webp)

This opens the same on-demand run form as the Task page's **Run** button. The quick-action menu is for on-demand runs only — to set up a schedule, open the Task page and use **New Schedule** instead.

## Configure the run

Both the on-demand and recurring forms share the same set of fields at the top.

![Create Task Run form with Environment, Configuration, Target Objects, task parameter fields, and Jackal Selection sections](/_fern-files/_img/5dfd8d0a382ce4fd32eb49fada159aaa23fbe0f7fd7b8a1e6ff99ffbf9d407b8.webp)

* **Environment**: The Environment to run the Task in. Configurations are scoped to a single Environment, so changing this resets the rest of the form.
* **Configuration**: A Configuration (or "Config") is a reusable bundle of parameter values, Target Objects, and Jackal selection for this Task. Pick an existing Config card to reuse its values, or click **Create New** to start from scratch.
* **Configuration Name**: A label for this Config so you can pick it up again later.
* **Target Objects**: The input Objects the Task should run against. Toggle between **Use Existing Set** to pull from a saved [Object Set](/guides/explorer/create-an-object-set) or **Select Target Objects** to pick Objects ad-hoc.
* **Task parameters**: Any [Input Parameters](/guides/automations/create-a-task#declare-input-parameters) declared on the Task render here as inline fields. The exact set varies from Task to Task. Required parameters are marked with a red asterisk.
* **Jackal Selection**: Where the Task runs. Pick **Cloud Jackal** to use Method's infrastructure, **Deployed Jackal** to run on any of your installed Jackals, or pick a specific Jackal by name.

## Run on demand

When the form is filled in, click **Launch** in the bottom-right corner. The Task starts immediately and the new run appears under the Task's **Runs** tab.

## Schedule a recurring run

Clicking **New Schedule** on the Task page opens a form with the same shared fields, plus a scheduling block at the bottom. The form's title is **Create Automation**, but the result is a recurring Task Run scoped to this Task.

![Create Automation form showing Environment, Configuration, Target Objects, parameter fields, and Jackal Selection](/_fern-files/_img/9efc36f19851c7074445632494a4418c54b55a201526b58a8c2c09b0fbd4986b.webp)

After filling in the shared fields, configure the cadence.

* **Run Every**: How often the schedule should fire.
* **Run on Days of Week**: The days the schedule is allowed to run. Toggle each day on or off.
* **Set Deny Slot times where this Automation should not run**: Time windows during which the schedule should not run, even if the cadence and day-of-week match. Pick a **Preset** or set custom **Start** and **End** times, then choose a **Timezone**. Use **+ Add Window** to add multiple deny ranges. The preview timeline shows green bars where the schedule is allowed to run; gaps are deny windows.
* **Schedule Enabled**: Toggle on or off to enable or disable the schedule without deleting it.

![Schedule form showing Run Every dropdown, Run on Days of Week toggles, Deny Slot windows with timezone and preview timeline, and Schedule Enabled toggle](/_fern-files/_img/1bf63a9dc5374296d8fc33260053cba36f8da7662f1f39bfbbc1038b163cf37c.webp)

Click **Create Automation** in the bottom-right to save the schedule. It will appear under the Task's **Schedules** tab.

> **Note**
>
> You can create multiple schedules per Task. Keep each one focused on a
> specific set of Target Objects so it's easier to track over time.