# Scheduler

## Requirements

Linux Control Center = 2.12.X or higher

## Overview

* The Schedule feature in the Linux Control Center platform provides a robust time automation capability. This feature allows you to schedule precise operations for individual Hosts, Host Groups or Workflow execution.
* The scheduling options cover all LCC *Actions* for single or recurring events, providing flexibility in the scheduling format.

## Objective

This document aims to demonstrate the step-by-step process for creating a schedule in Linux Control Center.

## Create a Schedule

1. Access the **Schedule** screen in the left side menu.

![](/files/tLhKhl0kdhoOgWzktGpX)

1. Click **Create**.

![](/files/FnCdKfKGWbSjBAzAF21l)

1. Fill in the **Name** field to identify the schedule.

![](/files/tDQtpVG1GZGSB90uDtre)

## Action Selection

1. The first step is to select which **Action** will be executed in the schedule.

{% hint style="info" %}
Only one action can be executed per schedule, and only one of the three options among *Host/Host Group, Discover, Workflow, Reports* can be selected at a time.

If it is necessary to execute more than one action in a single schedule, you must create a *Workflow* flow and schedule its execution for the desired time.
{% endhint %}

### Hosts / Host Groups

1. Check the first option to run an LCC *Action* on a Host or Host Group.

![](/files/qiDxJAwtFkt4paV7CMn4)

1. At least 1 **Host** or a **Host Group** must be selected.
2. It is also possible to run on an individual Host or Host Group simultaneously.

![](/files/yG6N1P2gDafpr1dqdhUD)

1. Choose the **Action** you want to run on the schedule.

![](/files/LoON4lewoxTdSUCK1fGj)

### Discover

1. Check the **Discover** option if you want to schedule the execution of a pre-configured **Discover**. This schedule allows you to run only 1 Discover.

![](/files/Gp0W8FLnvsXjkheuMwjN)

### Workflow

1. Click **Workflow** to schedule the execution of a pre-configured **Workflow**.

![](/files/fleBKiDkd6okqS5n21ck)

### Reports

1. Click **Reports** to choose which pre-configured Report will be created in the schedule.

![](https://gitlab.com/7dev-doc/linux-control-center/-/blob/main/pt-br/images/schedule/create_schedule)

## Schedule Type

* This step defines how many times and at what time the schedule will be executed.

### Once

* With this type of schedule, the *Action* will be executed only once and the schedule will remain saved in the LCC Console.

1. Check the **One Time** option to execute only once.

![](/files/NQqjCh1YWxdDRUrDwhy3)

1. Enter the **Time** you want to execute in the **Hour** field. (24-hour format)
2. Enter the **Minute** you want to execute in the **Minute** field. (0 to 59)

![](/files/bobggwOU066ih9jhRLfp)

1. Enter the day of the **Month** on which you want to execute the action in the **Date** field.

![](/files/nq7oI5bwp6R6sUHF4D2i)

### Repeatedly

* The *Repeatedly* scheduling type allows execution according to the 3 options below;

#### Every Minute

1. Check the **Minute** box and enter how many minutes the *Action* will be executed. This way, the action will be executed every X minutes defined. (1 to 59)

![](/files/IZSOPkk85pTzv8qM4AXs)

#### Daily

* This type of schedule executes the *Action* only once a day, at the configured time.

1. Enter the *Hour* of the day you want to execute the *Action* in the **Hour** field. (24-Hour Format)
2. Enter the *Minute* of the hour you want to execute the *Action* in the **Minutes** field. (0 to 59)

![](/files/6E3XHssv2shZ9cS005Dm)

#### Advanced

{% hint style="info" %}

* If you want the *Action* to be executed daily, just leave the **Day of Week** field blank(\*)

* If you want the *Action* to be executed monthly, just leave the **Month** field blank(\*)
  {% endhint %}

* This type of scheduling allows the action to be executed every *Day of the Week*, *Day of the Month* or every *Month*.

  ![](/files/y3uJtoJiA1E93Km0FFUQ)

1. Select the day of the week on which the *Action* will always be executed in the **Day of Week** field.

![](/files/5rznZPV40LZF3W7FKCLX)

1. Select the day of the month on which the *Action* will always be executed in the **Day of Month** field.

![](/files/Mt0IMEL0DGlBxSrt205M)

1. Select the month on which the *Action* will always be executed in the **Month** field.

![](/files/Uzt7HrXhxMMTDOvp2Mld)

## Save and Enable or Disable Schedule

1. Click **Save** to create the schedule.

![](/files/ao9EfvjL2xXZPLqOlSV4)

1. The screen of created schedules displays some information;

**Enabled/Disable**: Indicates whether the schedule is enabled or disabled.\
**Repeat**: Indicates that the schedule will occur periodically according to the date entered.\
**Last Run at**: Date of the last execution of the schedule.\
**Created at**: Date of creation of the schedule.\
**Updated at**: Date of the last change to the schedule.<br>

1. Click on the created schedule.

![](https://gitlab.com/7dev-doc/linux-control-center/-/blob/main/pt-br/images/schedule/create_schedule)

1. The **Enable Schedule** field allows you to Enable and/or Disable the Schedule. When Enabling, the schedule will be executed automatically according to the configuration.

![](https://gitlab.com/7dev-doc/linux-control-center/-/blob/main/pt-br/images/schedule/create_schedule)

1. It is also possible to *Delete* a schedule permanently by clicking the **Delete** button.

![](https://gitlab.com/7dev-doc/linux-control-center/-/blob/main/pt-br/images/schedule/create_schedule)


---

# Agent Instructions: 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:

```
GET https://docs.linuxcontrolcenter.com.br/en/scheduler.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
