...
| Excerpt |
|---|
As needed, you can schedule the execution of recipes in your flows jobs on a recurring basis. For example, if the source file of your flow your source data for the job is updated outside of the application on a weekly basis, you can define a schedule to execute the recipe job associated with the related imported dataset after the data has been refreshed. When the scheduled job successfully executes, you can collect the wrangled transformed output in the specified output location, where it is available in the published form that you have specified. |
To schedule a job, you must create the following configuration objects:
Define a schedule - For each flow you supported asset type, you can define a schedule. A schedule specifies one or more recurring times (triggers) when scheduled jobs for the flow are executed. For example, in a single schedule, you can specify daily trigger times for incremental updates and monthly execution times for rollups.
Tip Tip: The scheduler supports a modified form of cron job syntax. For more information, see cron Schedule Syntax Reference.
Define one or more scheduled destinations - When you specify a scheduled destination for a recipe, the recipe is upstream sets of transformation steps are executed whenever one of the schedule's execution times occurs. Scheduled destinations are specified like regular destinations.
Info NOTE: When a schedule for a flow is triggered, all transformation jobs upstream of recipes to generate the scheduled destinations destination are executed. Manual destinations are not generated. You cannot create schedules for individual outputs.
...
- One schedule cannot be applied to multiple flowsassets.
- You cannot create separate schedules for individual recipes assets within a flow . A schedule defined at the flow level applies to all recipes in the flow.Only a flow or workflow.
- Only an asset owner can create or modify a flowthe asset's schedule.
Data Management
...
