Modifying Scheduler Configuration for DBSync Project Tasks

1. Summary / Introduction This article explains how to change the scheduler configuration for project tasks that need to run at a set number of intervals to avoid synchronization gaps and better handle updates.

2. Problem / Issue

Synchronization workflows may need to run automatically or have their scheduled interval adjusted to better support record synchronization requirements.

3. Environment Environment: Cloud Workflow

Connector: QuickBooks Online

Integration Direction: Not Specified

4. Symptoms

No system errors are present in the logs. The synchronization intervals may be configured with long gaps between executions, which can delay or give the impression records are not processed or that the workflow requires a manual trigger.

Observed behavior included:

  • The synchronization workflow does not execute during certain time windows due to the scheduler configuration.

  • The interval between scheduled runs is too long, causing delays before updates appear in the source or destination system unless the workflow is manually triggered.

  • The scheduler interval may need to be adjusted to run more frequently to support closer synchronization timing.

The workflow itself functions correctly; however, updates may not be processed until the next scheduled execution due to the configured synchronization interval.

5. Root Cause Update the schedule run time interval for a desired project task to avoid doing manual syncs or to have a different time gap between already running intervals for better real time syncs

6.Solution / Resolution:

  1. Navigate to Projects within the DBSync application.

  2. Locate and open the relevant Project, then select the corresponding Task.

  3. Once inside the task, navigate to the Schedule tab located in the upper section of the task configuration page.

  4. Review the scheduler configuration:

  5. If no scheduler has been configured, create a new schedule entry.

  6. If a scheduler already exists and requires modification, locate the existing schedule and click the Edit icon (red pencil icon).

  7. Adjust the scheduler settings as required. This may include:

  8. Changing the interval type (minutes, hours).

  9. Updating the interval value (for example, changing the run frequency from 30 minutes to 15 minutes, or from 1 hour to 30 minutes).

  10. Confirm the updated scheduler configuration and click Save to apply the changes.

Once saved, the workflow will execute automatically according to the updated scheduler interval.

7. Additional Troubleshooting (Optional)

After modifying the scheduler configuration, the change will apply to future workflow executions. The updated interval may not be immediately visible in the logs until the next scheduled runs occur.

To confirm that the scheduler update is functioning correctly:

  • Review the DBSync workflow logs after some time has passed to verify the new execution frequency.

  • Confirm that log entries display “Scheduler/Run” in the Command column, indicating the workflow was triggered by the scheduler.

  • Verify that the Start Time in the logs reflects the newly configured interval.

For example, if the scheduler interval is changed from 1 hour to 15 minutes, earlier logs will still show executions occurring every hour. After the new schedule takes effect, subsequent log entries should appear approximately every 15 minutes, confirming that the updated scheduler configuration is working as expected.

8. Impact If the scheduler interval is configured with large gaps between executions (for example, several hours), updates made in the source or destination systems will not be processed until the next scheduled run occurs. During this time, records may appear unsynchronized even though the workflow itself is functioning correctly.

Adjusting the scheduler interval to run more frequently helps reduce the delay between data changes and synchronization. In many integrations, shorter intervals (such as 15–30 minutes) are commonly used to support near real-time data updates, depending on the workflow requirements and system capacity.

Last updated