Execution of a job when one of the packages fails

Hi @Thomas Lind 

Do you think that it is an issue?

Hi @rvgfox

If you added two transfer tasks from the same data source in the ODX and they contained different tables, which is what you would do as you wouldn’t add two packages with the same tables. Then I don’t see why you wouldn’t run the second package as it could run fine due to it being other tables. Depending on what the error is, it could affect both packages, but if the other is successful, you would not have to run the first one again.

The same goes for execution tasks in different data sources, one may work fine and the other not. Why should that stop another data source from running.

If you use Execution packages, it is possible to avoid it running just as before, you need to add only the first package and set it to run the other package on success.

You can also do it like this.

So each package is a sub package and they have individual retry options and if one fails it will not attempt the next package.

@Thomas Lind In my case, the fist package it’s the DW and the second the SSL model.

The two tasks are running on separate instances, so essentially similar to if it was two tasks in the same data source, or different data sources.

There is no option to relate any tasks across instances. The only way you can get a bit of this is the data on demand option.

So this is a new feature. There are some other ideas that are a little bit like this, but not completely.

I will make this an idea.

@Thomas Lind In this moment, the only way that I know to be sure thet the SSL instance it is not proccesed if the DW fails it’s to use an external power shell to update the SSL model.

There is a better way?