Creating a scheduler

Use this procedure to create a scheduler for a scenario within a project.

1. From the left navigation menu, select Projects. The Projects dashboard is displayed.

2. Select the project for which you want to create a scheduler. You can create schedulers for different scenarios in a project.

   The Canvas page is displayed.

3. Click the Scheduler tab on the project navigation menu on the left to open the Scheduler page.

1. Do one of the following:

• Click the plus icon on the top right-corner of the page.

• Click the +New Scheduler option to create a scheduler. However, you can only view this option when there are no schedulers created in this project.

The following page is displayed where you can create a scheduler to run this data pipeline at the set time interval.

1. Click the default scheduler name to provide a custom name on the top.

1. Select the scenario on which you want to run the project flow at the scheduled frequency.

2. Select the scheduler frequency. Possible values:

   • Daily - This displays Hrs and Min. drop-down to select the time at which the job should be triggered.

   • Weekly - This displays days in a week and time at which the scheduler should be run.

   • Cron - This displays the unix-corn format to create a scheduler.

3. View the project canvas.

4. Click Save to create the scheduler. This also enables the +Destination option to configure the data connector to which you can publish the generated output datasets or the input dataset.

   You can see the project variables button only if the variables are defined at the project level. After creating the scheduler, you can change the value in project variables.

   
5. Click + Destination. This opens the Destinations side panel.

Note: This button is enabled only if you have configured external data sources in your workspace.

1. Click + DESTINATION.

2. Select the dataset that you want to add to the destination. If the dataset list is huge, you can use the search option to search for the dataset you want.

3. Select the destination from the drop-down list. You can only view the list of external data sources configured under this tenant excluding Snowflake and Fivetran connectors.

ℹ️ Info: When you select the SQL connector to synchronize or copy the output dataset generated after running the project, the table name column is displayed. Here, you can provide the table name and select either "Append" or "Replace". Opting for the "Append" option will append the dataset to the existing one, provided both datasets share the same schema. Alternatively, selecting the "Replace" option will replace the existing dataset with the new one.

If you choose the data connector as MongoDB, you can provide the database name and collection. In the event that the provided collection name already exists, the new dataset will be appended to the existing collection.

1. Provide the destination folder and destination file name to save the file in the destination folder with the new file name after the job is run every time at the scheduled time.

1. Select the To create new file for every run check box to create a new file after every job run. The new file will be saved with the RUN ID. Clearing this check box overrides the existing file.

2. Click Save to save this destination. This button is enabled only after you select all the required destination fields.

   Note:

   You can store files in multiple destinations. To add another destination, click + DESTINATION. If you want to remove any destination, click the delete icon.

   If you no longer want to save the output to the configured destination, you can use the delete icon to delete the destination.

   
3. Close the window after configuring the destination for the job. Once the destination details are set, the destination node will appear on the scheduler canvas.

4. Click GLOBAL VARIABLES to change the configured parameters for this job.

   Note: The GLOBAL VARIABLES button is enabled only when the global variables are declared at the project level. To configure global variables, refer configuring global variables at a project level.
5. Change the value for the key. Please note that you cannot change the key.