Schedule data
Schedule a date and time to build or export a pipe or refresh a third-party data source.
You can schedule a date and time to perform the following actions:
Build a pipe.
Export a pipe.
Refresh a third-party data source.
Set the build, export, or refresh for the current date or later, or at different intervals. For example, you can create an hourly, daily, weekly, or monthly schedule.
If you choose an hourly schedule, do not schedule exports more frequently than every 15 minutes.
If you choose a daily schedule, you can have it export every day, every other day, every third day, and so on.
If you choose a weekly schedule, you can pick specific days of the week, and more than one day in that week, such as Monday, Wednesday, and Friday.
If you choose a monthly schedule, you can pick the frequency and the date, such as every two months on the 10th day.
Important
The Scheduler exports the most recent scheduled time. If you deactivate the schedule close to the time you previously scheduled and reactivate it right after the time, it exports. For example, if you deactivate the job at 11:59 am for a noon export and reactivate it at 12:01 pm, the Scheduler checks when the last job was exported and knows that the noon job didn't export. Since you reactivated the schedule, it will export. If you have a daily schedule and the last scheduled export was over 24 hours, the job will not export.
If you have multiple schedules exporting simultaneously, the last one completed appears in the Scheduler.
Daylight saving time and schedule time zones
The following section details how the Scheduler works with daylight saving time.
Calendar-based schedules: Native Varicent ELT daily, weekly, and monthly schedules account for daylight saving time (DST), preserving the scheduled local clock time in the selected schedule time zone.
Hourly schedules: Hourly schedules run at fixed elapsed-time intervals. For example, during spring-forward, an hourly schedule can run at 00:30 EST → 01:30 EST → 03:30 EDT. Although the displayed clock skips an hour, executions remain one hour apart.
Execution versus display: The schedule’s selected time zone determines execution. Changing the organization's time zone affects timestamp display, not schedule execution.
Timestamp display: When no organization time zone is configured, timestamps use the user’s browser or operating system time zone. If an organization's time zone is configured and observes DST, displayed timestamps reflect its changing UTC offset.
Admin configuration: The organization's time zone can be specified or edited in the management portal. Confirm whether this administrative detail belongs in customer-facing scheduling help or separate configuration guidance.