This should be an easy fix. And todays workaround has side-effects.
Somtimes you want Task B to run after Task A, regardless of A failed or not.
Workaround
Today we can create a new task event trigger, if EITHER a tasked executed successfully, OR if it failed.
![vegard_bakke_0-1628867073183.png vegard_bakke_0-1628867073183.png](https://community.qlik.com/t5/image/serverpage/image-id/60084iCD02F00279056BA3/image-dimensions/562x111?v=v2)
You'd think that we could add two tasks under the Triggers menu. But no. Any task already used, is deliberately removed from the list.
![vegard_bakke_1-1628867395485.png vegard_bakke_1-1628867395485.png](https://community.qlik.com/t5/image/serverpage/image-id/60086i6CEB12E90975BD4C/image-size/medium?v=v2&px=400)
The workaround is to add two trigger, both for the same task, both with different names.
Side-effects
Having two triggers, causes the chain windows to show double duplicates for all tasks that have been chained together.
![vegard_bakke_2-1628867559983.png vegard_bakke_2-1628867559983.png](https://community.qlik.com/t5/image/serverpage/image-id/60087i5154D115F43F74F8/image-size/medium?v=v2&px=400)
Solution
A simple solution would be to allow a trigger task for:
- Task successful
- Task failed
- Task failed/successful
Please add this. Shouldn't be hard.
Best regards,
Vegard Bakke