---
title: "How to configure Automatic Check schedule parameters"
description: "Optional parameters for Action Jail in Automatic Check schedules: form or JSON editor and list indicator."
---

# How to configure Automatic Check schedule parameters?

In **Automatic Check**, you can pass **additional parameters** to the selected Action Jail function — the same values the action receives in a scenario or when testing in Action Library.

## When you need this

- The Action Jail function expects parameters (for example, URL, ID, flag) and fails without them.
- You want one action on multiple schedules with **different** parameter sets.
- You need a scheduled check with the same data as in a production scenario.

## What to know

- **Parameters are optional** — if you leave them empty, the schedule behaves as before (no UI parameters).
- **Editor** — **Form** (when the action defines a field schema) or **JSON** (arbitrary object).
- **List indicator** — shows that a schedule has parameters configured.
- **Do not store secrets** (passwords, API keys) in schedule parameters — use [Scenario secrets](/en/settings/how-to/manage-action-credentials.md); actions should read secrets from the vault, not from schedule fields.
- The feature is **enabled by default** after upgrading to 5.9.0. To disable the parameters UI, contact your root administrator.

## Before you start

- [x] You have access to **Settings → Automatic Check**.
- [x] The Action Jail function exists and was tested (for example, in Action Library).
- [x] You know which parameter fields the action expects (see action docs or schema in Action Library).

If you have no schedules yet, start with the [first schedule tutorial](/en/settings/tutorials/first-automatic-check-schedule.md).

## Step-by-step

### 1. Open the schedule form

1. Go to **Settings → Automatic Check**.
2. Click **Create schedule** or **Edit** next to an existing row.

### 2. Select Action Jail

1. In **Action**, pick a function from the library.
2. Use the **group filter** to narrow the list if needed.
3. Open **Documentation** or **Action Library** to verify expected parameters.

### 3. Set parameters

1. Scroll to the **Parameters** block (right column in the two-column layout).
2. Choose a mode:
   - **Form** — fill fields from the action schema.
   - **JSON** — enter an object manually (for example, `{"baseUrl": "https://api.example.com", "timeout": 30}`).
3. Ensure JSON is valid (JSON mode highlights errors).

### 4. Save and verify

1. Set the **interval** (cron) as for any schedule.
2. Click **Save**.
3. In the schedule table, confirm the parameters indicator appears.
4. Wait for the next run or verify logs/results per your process.

## Related

- [Create your first Automatic Check schedule](/en/settings/tutorials/first-automatic-check-schedule.md)
- [View system status](/en/settings/how-to/view-system-status.md)
- [Manage scenario secrets](/en/settings/how-to/manage-action-credentials.md)