Skip to main content Skip to complementary content

Scheduling plans

Define how frequently you want to run your plan.

Note that schedule updates that are made within three minutes prior to the scheduled execution time immediately impact the execution. For this reason, avoid making schedule changes when an execution is about to be triggered.

Before you begin

If parallel run is not allowed for the plan, for an optimized design it is recommended to leave at least a one minute margin between the end of the first run and the beginning of the next one.

About this task

You can define multiple time triggers for the same plan.

You can also schedule the run of plans through the public API or a webhook, besides the Talend Management Console user interface.

You can have a webhook or 15 other triggers including Once, Daily, Weekly, Monthly and Cron types for each plan.

You cannot add new triggers if you already had a webhook. You can delete the webhook and add other triggers when editing the plan or you can also copy the plan if you need both.

Triggers must be separated by at least five minutes.

Information noteNote: When you edit the schedule of a single-triggered plan in the UI, this plan is converted to multi-triggered. Once done, you need to use GET /executables/plans/{planId}/schedule endpoint to get plan schedule details.

The same plan can only be in the execution queue (in Pending or Running status) maximum 50 times in a 60-minute time period. If you have scheduled a plan through the public API or a webhook to run more times than that, any new execution that would be added to the queue will fail after the limit is reached.

Procedure

  1. If you are editing your plan after it has been created, go to its details page, then click the Edit trigger icon next to Trigger.
  2. Optional: Select the Allow parallel run of this plan option to be able to start another run of this task before the previous one is over.
    Job tasks included in this plan and whose Engine is set to Cloud Engine, Cloud exclusive, Remote Engine or cluster will run in parallel.
    This feature is not available for plans containing pipelines.
  3. Click the Add trigger icon.
    If you select the manual trigger, you must start the run from the plan details page by clicking Run now.
  4. Enter the name of the trigger.
    The name must contain only alphanumeric, -, # and _ characters. Spaces and other special characters are not allowed.
  5. Select the trigger type from the Trigger type drop-down list.
  6. In the Location (time zone) field, define the time zone for your executions.
  7. Enter the start date of the run.
  8. Define the frequency of the run in days/weeks/months.
    For example, if you want to run your plan every day, enter 1.
  9. To run the plan at specific times during the day, select At specific time(s) from the Repeat drop-down list and enter the execution times below.
  10. Enter or select from the drop-down list the first execution time.
    If you want to run the plan several times a day, click Add new and enter/select the appropriate time. Repeat this procedure as many times as needed.

    Example

    Page to define execution time.
    The plan will run at 09:00, 14:00, and 17:00 every day.
  11. To run the plan at intervals, select Specific intervals from the Repeat drop-down list.
    1. Set the interval time in minutes in the Repeat every field.
    2. Enter the start time for the execution in the Repeat from field.
    3. Enter the end of executions in the Repeat to field.

    Example

    Page to set up task execution intervals.
    The execution will happen every 10 minutes every day between 06:00 and 18:00.
  12. Click Save and close.

Results

A confirmation message is displayed at the top of the page. You are redirected to the plan details page. The schedule you have defined appears under Trigger > Trigger type.

You can also view the schedule in the Plans tab. Click the Triggers and plans icon.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!