--- title: "Define Characteristics" slug: "define-characteristics-scheduler-module" tags: ["Scheduler Properties", "General Settings", "Configuration"] updated: 2026-05-20T13:04:51Z published: 2026-05-20T13:04:51Z canonical: "help.symphonysummitai.com/define-characteristics-scheduler-module" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.symphonysummitai.com/llms.txt > Use this file to discover all available pages before exploring further. # Define Characteristics ## General Properties The first step in the Scheduler process is to configure General Properties. To configure the General Properties, define the Scheduler Name, Scheduler Type, Description, Table, Tenant, and Scheduler Owner. For more information, refer to the field description table below. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1712731722784.png?sv=2026-02-06&spr=https&st=2026-11-06T06%3A53%3A25Z&se=2026-11-06T07%3A53%3A25Z&sr=c&sp=r&sig=E4tUk0R9HcRAbjV3KP5zYL%2BelyIJWSePxsHttlVFngk%3D)Figure: General | **Field** | **Description** | | --- | --- | | Scheduler Name* | Specify a unique name for the Scheduler which conveys the task clearly. For example, Auto resolve old incidents. | | Scheduler Type (To be incorporated) | Specify the type from the drop-down menu. For example, Custom Event. Note - When the **Scheduler Type** is selected as **Custom Event**, the Scheduler invokes the following four Actions i.e. Create Record, Update Fields, Notify Recipients, and Call API. - When the **Scheduler Type** is selected as Standard Event, the Scheduler Action invokes the System Defined Actions. The condition step is not applicable. | | Scheduler Description | Enter additional details about the Scheduled activity. For example, Incidents more than 2 months old. | | Execute At* | Choose the monitoring source on which the Scheduler should run from the drop-down in the particular field. For example, Web Server or Proxy Server. | | Runs at Proxy* | Specify the server from the list of Proxy Servers. (This field is enabled when Proxy Server is selected in Execute At | | Table* | Select the table at the module level on which the Scheduler will be configured. Note The Table field is invalid when the Scheduler Type is selected as Standard. | | Tenant* | Specify the Tenant from the drop-down list. It will be based on the Domain and Sub Domain selected. | | Scheduler Owner* | Specify the Scheduler Owner who will be intimated for any problem/configuration failure. | | Active | Schedulers can be activated/deactivated using the Active Switch. It must be turned on while creating a new Scheduler. Note Do enable the Active Switch for a new Custom Schedule. | *An asterisk (*) represents mandatory field.* #### Configurations for Agent Based Discovery To enable Agent-Based Discovery, a scheduler must be configured to process the agent store-and-forward data received from endpoints. This scheduler runs at the Proxy Server and periodically processes the collected discovery data. To configure the Scheduler, perform the following steps: 1. Navigate to **Design Studio**. Select the module as **Asset Management**. Navigate to **Designers** > **Scheduler**. The **Scheduler List** page is displayed. 2. Click **New.** The **General** page is displayed. Specify the field value for **Runs at Proxy** as mentioned in the below screenshot. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-K9Z0OUB5.png?sv=2026-02-06&spr=https&st=2026-11-06T06%3A53%3A25Z&se=2026-11-06T07%3A53%3A25Z&sr=c&sp=r&sig=E4tUk0R9HcRAbjV3KP5zYL%2BelyIJWSePxsHttlVFngk%3D) Figure: Asset Management - Scheduler - General 3. Click **Next**. The **Frequency** page is displayed. 4. Click **Next**. The **Actions** page is displayed. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-78N1CXA4.png?sv=2026-02-06&spr=https&st=2026-11-06T06%3A53%3A25Z&se=2026-11-06T07%3A53%3A25Z&sr=c&sp=r&sig=E4tUk0R9HcRAbjV3KP5zYL%2BelyIJWSePxsHttlVFngk%3D) Figure: Actions 5. Click **Next** to save and to activate the scheduler configuration. Once configured, the scheduler will automatically process the agent store-and-forward discovery data