I know that xtrigger valus are stored in the suite log database - is there a way to “reset” an xtrigger for the following workflow I’ve concocted by way of illustration:
- Task "consume in suite “foo” depends only on an xtrigger that checks on the availability of file “F”
- File “F” is produced by a task “produce” in suite “bar”
- A problem occurs (disk filled up, so file present but with incomplete output
- task “consume” and several tasks upstream of “consume” need to be re-run
- task “consume” in suite “foo” is reset to waiting[*]
- task “produce” in suite “bar” is re-triggered to rewrite file “F”
At this point, because the xtrigger was already satisfied, task “consume” in suite “foo” should fire again, but in this case too early because task “produce” in suite “bar” hasn’t finished yet and the xtrigger is picking up the production of file “F” from the last time around, not the current execution. What I think I want to do is reset/clear the xtrigger dependence, forcing the trigger function to execute again as the task is waiting until the file is reproduced successfully and the run can pick up where it left off.
How would I accomplish this? I didn’t see this in the documentation, but I was reading quickly.