Scheduling data generation
Required workspace permission: Run data generation
Not available for Structural free trials, or for expired pay-as-you-go accounts.
You can also configure data generation to run on a regular schedule. For example, if new data is added regularly to your source database, then you might want to automatically run data generation jobs to transform the new data.
To schedule the job, you configure one or more configurations. Each configuration includes a cron expression to specify the schedule.
Creating and editing a job schedule
You manage the job schedule from Jobs view.
To create a schedule for a job, click Create Schedule.
To edit an existing job schedule, click Edit Schedule.
Set up the schedule configurations, then click Save.
Adding a configuration to a schedule
To add a configuration to the schedule:
Click Add Configuration.
By default, the configuration is active, and Active is in the on position. To have Structural ignore the configuration, toggle Active to the off position.
In the Cron Expression field, provide the schedule expression. The default value is
0 0 * * *
, which means to run the job every day at midnight.From the time zone dropdown list, select the time zone to use for the schedule.
Overview of the cron expression syntax
A cron expression is made up of five values separated by a space.
<minute> <hour> <day of month> <month> <day of week>
Where:
Here are some example expressions:
Removing a configuration from the schedule
To remove a configuration from the schedule, click its Delete option.
If you remove all of the configurations and then save, the job is no longer scheduled.
Scheduled jobs and other workspace configuration
When a job runs on a schedule, you cannot configure the options that are available from the Confirm Generation panel when you run data generation manually.
Subsetting
Upsert
If this is in the on position, then the scheduled job does both data generation and upsert.
If this is in the off position, then the scheduled job only does the data generation to the intermediate database.
Diagnostic logging
Last updated