Schedule Triggering: The new way to setup data loading process

Jiri Tobolka

We’ve just released an interesting new feature to our Data Integration Console that allows you to set up the schedule in a new way. Till today, the only option is to run the schedule in a specific time and period. You are not able to setup the schedule being executed by the other schedule. Well this is no more true. There is a clear use case:

I want to run the schedule after the previous one is successfully finished.

Let’s do that!

Setting Up the Trigger for New Schedule

1) Go into the Data Integration Console and create a new Schedule (Nothing exciting so far.)

New Schedule

2) Create another Schedule and select the “Run after” instead of i.e. “Run every day”.

Another Schedule

3) The upload.grf is set up to run after the previous schedule is successfully finished. Click on Schedule.

Runs after previous

4) Great! Now the second graph runs after the first has been finished. (This is exciting!)

Scheduled are Ready

Perfect, as you can see you can very easily “chain your schedules” directly in the Data Integration Console. But what if I already have some existing schedules?

Setting up the trigger for existing schedules

If you already have two schedules that are executed in specific time, you can easily change this and use this new feature.

1) We have two schedules both executed every day in specific time.

Time schedules

2) Edit the ga.grf to run it after upload.grf is finished.

Editing schedule

3) Easily save the new settings.


4) Yes! We have just scheduled the graph to being triggered by the other graph.


Thanks to that, now it’s not necessary to rely on the hope 20 minutes will be enough for running the 1st schedule and that the 2nd schedule will have all the necessary data available. The 2nd schedule will run automatically shortly after the successful finish of the 1st one.

Looping the schedules

Remember that you are not able to setup a loop. You are not able to set up the schedule to being executed by the same schedule. Only exception is “Retry After” option, but it works only for failed schedules. See the diagram below as example:


Remember that schedules run the same (in the separate sandboxes) as it was till today. The only change is in the way how the execution is triggered. If you need more information, check out the full documentation. Let us know if you have any feedback or you just love the new feature!

Dev's Newsletter

Subscribe Now