Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DEV and version r0712

D toc


As needed, you can use the Automator to schedule the execution of recipes in your flows on a recurring basis. For example, if the source file of your flow is updated outside of the application on a weekly basis, you can define a schedule to execute the recipe associated with the related imported dataset after the data has been refreshed. When the scheduled job successfully executes, you can collect the wrangled output in the specified output location, where it is available in the published form that you have specified.

  • This feature was formerly known as, "scheduling."

To schedule a job, you must create the following configuration objects:

  1. Define a schedule - For each flow 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: The scheduler supports a modified form of cron job syntax. For more information, see cron Schedule Syntax Reference.

  2. Define one or more scheduled destinations - When you specify a scheduled destination for a recipe, the recipe is executed whenever one of the schedule's execution times occurs. Scheduled destinations are specified like regular destinations in flow view.


    NOTE: When a schedule for a flow is triggered, all of recipes to generate the scheduled destinations are executed. Manual destinations are not generated. You cannot create schedules for individual outputs.

For more information on the scheduling objects, see Object Overview.


  • One schedule cannot be applied to multiple flows.
  • You cannot create schedules for individual wrangled datasets within a flow.
  • Only a flow owner can create or modify a flow's schedule.

Data Management


NOTE: Since scheduled destinations are re-populated with each scheduled execution, you must determine how you wish to manage the data that is published to each location. Data management should be done outside of

D s product

  • Import: Before each scheduled execution, you should refresh the source of the imported dataset with new data outside of
    D s product
  • Execution: Please verify that the publishing settings for your scheduled destination are consistent with how you are using the results. For example, if the scheduled destination creates a new file with the same name for each execution (replace), you must move the generated file out of the output location before the next scheduled execution.
  • Output: You must collect the generated results. While you can export the job's results through the Jobs page, you may find it easier to use an external scheduler to gather the results and forward to the downstream consumer of them.

Flows for scheduling


Tip: When a schedule is executed, all outputs in a flow are generated, even if they are unused. For better performance on larger flows, you can create a separate flow that contains only the references back to the objects in the source flow that you wish to have scheduled. As an additional benefit, this separation keeps development and scheduled execution in separate flows.

Schedule a Job

Schedules and scheduled destinations are defined through Flow View.


Tip: You can create schedules for datasets with parameters and apply overrides through Flow View at runtime. See Flow View Page.

For more information, see Schedule a Job.

Track job execution

You can monitor a scheduled job like any other job in the application. See Jobs Page.


See Configure Automator.

via API

Not supported in this release.