Treasure Data supports these flexible scheduling options:
- daily
- weekly
- monthly
- start date
- end date
Info |
---|
When you add a schedule to your workflow, if you attempt to select New Run to run the workflow immediately, you will likely get an error. The workflow must run at the specified scheduled time. |
Set a Daily Schedule
Info |
---|
If a daily workflow schedule does not progress as expected, it might be due to one of two things: - You didn't set a timezone, and therefore the default timezone of UTC is changing the daily schedule.
An existing daily session has already started, and therefore, your daily schedule will run the next day. Learn more at TD Workflow FAQs.
|
In the following example, the workflow runs every day.
Numbered Headings |
---|
start-numbering-with | 1 |
---|
start-numbering-at | h5 |
---|
|
Open TD ConsoleNavigate to Data Workbench > Workflows.Open an existing workflow or create a new one.Select Launch Project Editor.
Code Block |
---|
firstline | 1 |
---|
linenumbers | true |
---|
| _export:
td: database:
workflow_time
timezone: America/Chicago
schedule :
daily>: 07:00:00 |
|
Set a Weekly Schedule
In the following example, the workflow runs every Sunday at 09:00.
Numbered Headings |
---|
start-numbering-with | 1 |
---|
start-numbering-at | h5 |
---|
|
Open TD ConsoleNavigate to Data Workbench > Workflows.Open an existing workflow or create a new one.Select Launch Project Editor.
Code Block |
---|
firstline | 1 |
---|
linenumbers | true |
---|
| _export:
td: database:
workflow_time
timezone: America/Chicago
schedule :
weekly>: Sun, 09:00:00 |
|
Set a Monthly Schedule
In the following example, the workflow runs on the 1st day of every month at 10:00.
Numbered Headings |
---|
start-numbering-with | 1 |
---|
start-numbering-at | h5 |
---|
|
Open TD ConsoleNavigate to Data Workbench > Workflows.Open an existing workflow or create a new one.Select Launch Project Editor.
Code Block |
---|
firstline | 1 |
---|
linenumbers | true |
---|
| _export:
td: database:
workflow_time
timezone: America/Chicago
schedule :
Monthly>: 1, 10:00:00 |
|
Set a Start Date
In the following example, the workflow run starts on 2022-10-05 and runs daily at 7:00 a.m.
Numbered Headings |
---|
start-numbering-with | 1 |
---|
start-numbering-at | h5 |
---|
|
Open TD ConsoleNavigate to Data Workbench > Workflows.Open an existing workflow or create a new one.Select Launch Project Editor.
Code Block |
---|
firstline | 1 |
---|
linenumbers | true |
---|
| _export:
td: database:
workflow_time
timezone: America/Chicago
schedule :
start>: 2022-10-05
daily>: 07:00:00 |
|
Set a Start Date with Start Time
In the following example, the workflow run starts on 2022-10-05 and runs daily at 7:00 a.m.
Numbered Headings |
---|
start-numbering-with | 1 |
---|
start-numbering-at | h5 |
---|
|
Open TD ConsoleNavigate to Data Workbench > Workflows.Open an existing workflow or create a new one.Select Launch Project Editor.
Code Block |
---|
firstline | 1 |
---|
linenumbers | true |
---|
| _export:
td: database:
workflow_time
timezone: America/Chicago
schedule :
start>: 2022-10-05
daily>: 07:00:00 |
|
Set a Start and End Date
Setting an end date can help you end campaign workflows on a set schedule, so there is no accidental running of a workflow after completing a campaign.
How End Dates Work
- The workflow scheduler stops scheduling the workflow past YYYY-MM-DD.
- The time for the end schedule always defaults to "end date HH:MM:SS"; the user-defined date and not exceeding "end date 23:59:59".
Example
In the following example, the schedule runs the workflow daily from 7:00 a.m until 2022-10-04.
Numbered Headings |
---|
start-numbering-with | 1 |
---|
start-numbering-at | h5 |
---|
|
Open TD ConsoleNavigate to Data Workbench > Workflows.Open an existing workflow or create a new one.Select Launch Project Editor.
Code Block |
---|
firstline | 1 |
---|
linenumbers | true |
---|
| _export:
td: database:
workflow_time
timezone: America/Chicago
schedule:
daily>: 07:00:00 end>:2022-10-05
|
|