Schedule an operation to run automatically in Jitterbit Studio

Introduction

Operation schedules trigger one or more operations at configured times without manual intervention. You can configure schedules as simple as "every day at 9 AM" or as specific as "every 15 minutes on weekdays between 8 AM and 6 PM."

When a scheduled operation has operation actions configured, any downstream operations run automatically as part of the same chain.

Schedules are created and assigned in Studio, then deployed with the operation. After deployment, you can enable or disable schedules at any time from the Management Console without redeploying.

Part 1: Create a schedule

Step 1: Open the Schedules tab

1. On the design canvas, click the calendar icon on the operation to open the Schedules tab of the operation settings. Alternatively, double-click the operation, then select the Schedules tab.

2. In the Schedules tab, click Create New Schedule to open the schedule configuration dialog.

Step 2: Configure the schedule

1. Schedule name: Enter a descriptive name that reflects the schedule frequency or the operation it serves, such as Every 15 Minutes or Nightly Contact Sync. The name must not begin or end with a space.

2. Occurrence: Select the days on which the schedule should run:

   • Daily: Runs every day, or every N days. Enter the interval in the Every [#] Day(s) field.

   • Weekly: Runs on selected days of the week. Enter the week interval in Every [#] Week(s), then click the day buttons to select which days to include. At least one day must be selected.

   • Monthly: Runs on a monthly basis. Choose one of two options:

     • Day [#] of Every [#] Month(s): Enter a specific day of the month and the month interval.
     • The [1st/2nd/3rd/4th/Last] [Day of Week] of Every [#] Month: Select the occurrence and day of week, then enter the month interval.

3. Frequency: Select how often the schedule triggers within each active day:

   • Occurs Once at [time]: Triggers the operation once at the specified time. Enter the hour and minute in HH:MM format and select AM or PM.

   • Occurs Every [#] [Minutes/Hours] Starting at [time] and Ending at [time]: Triggers the operation repeatedly at the specified interval throughout a time window. Enter the interval, then the start and end times.

     Tip

     The time you enter is interpreted in the time zone of the agent running the operation, not your local browser time. Cloud agents always run in UTC. If you are using private agents, their time zone is determined by the operating system of the agent machine.

     For predictable schedule behavior, use UTC. If your organization requires a consistent time zone across all schedules, an administrator can enable the Override Schedule Agent Time Zone setting in organization policies and set it to Etc/UTC.

4. Duration: Set when the schedule becomes active and, optionally, when it expires:

   • Start Date: Defaults to today. Use the date picker to select a different start date.
   • End Date: By default, the schedule runs indefinitely. Click Add End Date to set an expiration date. The schedule remains active through the end of the end date.

5. Click Save to create the schedule.

Part 2: Assign the schedule to the operation

Step 1: Select and assign the schedule

1. Back in the Schedules tab, open the Schedule menu and select the schedule you just created.

2. Click Assign. The tab updates to show a summary of the assigned schedule, and a calendar icon appears on the operation on the design canvas.

   Note

   Only one schedule can be assigned to each operation. Assigning a new schedule replaces the existing one.

Step 2: Set the schedule policy

After assigning a schedule, set the Schedule policy to control what happens if a scheduled run is triggered while a previous run of the same operation is still executing:

• Skip if already running (default): The new scheduled run is skipped. Use this setting for most integrations to avoid processing the same source data concurrently.

• Always run: The operation runs regardless of whether a previous run is still in progress. Use this only when your integration explicitly requires concurrent execution and you have confirmed that running the operation concurrently will not result in duplicate data processing.

Part 3: Deploy and manage the schedule

Step 1: Deploy the operation

Schedules assigned in Studio do not activate until the operation is deployed.

Deploy and run the operation to push the schedule to the Harmony platform. After deployment, the schedule activates and the operation runs at the next scheduled time.

Step 2: Manage the schedule from the Management Console

After deployment, you can enable or disable the schedule at any time from the Management Console Projects page without redeploying.

The Projects page provides two ways to control schedule status:

• Per operation: On the Operations tab, use the toggle in the Operation Status column to enable or disable the schedule for a single operation.

• Across all operations: On the Schedules tab, use the toggle in the Schedule Status column to enable or disable a schedule across every operation it is assigned to.

  Note

  Disabling a schedule at the project level overrides individual operation settings. The Effective Status shows as disabled even when the schedule is enabled for a specific operation.

Verify the integration

After deploying, confirm the schedule is active:

1. On the design canvas, verify that the calendar icon appears on the operation. Hover over the icon to see a summary of the assigned schedule.

2. In the Management Console, go to Projects and open the Schedules tab. Confirm the schedule is listed and its Schedule Status toggle is enabled.

3. After the next scheduled time passes, open the operation logs and confirm the operation ran successfully at the expected time.

If the operation does not run as expected, confirm the operation has been deployed after the schedule was assigned, and check that the schedule is enabled in the Management Console. For additional troubleshooting steps, see Troubleshoot schedules in the operation schedules reference.