Scheduled excecution: prioritization not working

Hi Support,


We are experiencing an issue with the prioritization in our execution package. 
Our trip table is updated with an update script using data from the number_per_trip table.

However, the trip table is loaded before the numbers_per_trip table. This results in missing new data in the trip table as the number_per_trip table has not yet been loaded before the script action is executed. We would like to change the loading order of these tables and have tried to do this by adding prioritization. This has no effect on the load whatsoever. I cannot find out what the problem is.

Are there any settings blocking the prioritization feature or are we using the feature in the wrong way?

See settings below.



Best answer by Thomas Lind 16 May 2023, 10:47

View original

3 replies

Userlevel 6
Badge +5

Hi Freek

It does not make your executions run fast when using anything other than individual tables as the exclude step. This is because it reads through all the tables across all the excluded parts before choosing to not execute them.

It would be better to flip it around and add only what you want to execute, or to add individual tables to the exclude steps area.

Also the whole order of execution could be due to the updated table not being related to the  numbers_per_trip table. You can add custom relations using the Object Dependencies menu.

So set these on the table that uses the insert, so it runs before it is being used.

Hi Thomas,


Thanks for the quick reply. I will look into the execution configuration. Great advice.


The object dependency will cause a circular dependancy. This is also the reason why I am using an update script to update the table. As a lookup will also result in a circular dependancy. 


Is there any other way to avoid this and still have the correct execution order?


Userlevel 6
Badge +5

Hi Freek

If you have circular reference errors you should focus on resolving that so you can relate the tables. One way is to use the same source table across multiple tables, only getting the necessary data and then merging it back in at a later point.

Alternatively splitting out the existing data in to multiple tables using table inserts and then adding it back at a later point. If you need more rows than exist in the original table custom table inserts can be used. They do have the same issues with relations, as you will have to manually set them with the Object dependencies.

A bit like is explained in this old guide