Triggering build_marts runs rxnorm a second time even if it just ran to completion

[jrlegrand]

Problem Statement

The rxnorm DAG has to be turned "on" for build_marts to run it. Turning rxnorm "on" automatically runs it.

I normally do this workflow:

1. Turn rxnorm DAG "on" which triggers it to run. I do the same for the 3 FDA DAGs which automatically trigger to run. I also turn rxclass_atc_to_product and rxnorm_historical on but they don't automatically trigger to run.
2. After rxnorm runs to completion, I turn build_marts "on" and trigger it to start.
3. This triggers ONLY rxnorm to start running a second time which takes like 7 extra minutes or so to run AGAIN - which just delays the other two DAGs to start (rxclass_atc_to_product and rxnorm_historical)

Criteria for Success

This may be only an issue the first time I run build_marts, and ideally I could just leave build_marts on and it would run by itself on a regular basis - this just isn't how I have been using it and this has been mildly annoying.

For this to be successful, I would like build_marts to know that rxnorm was just run to completion and to not re-run it when the workflow above is followed.

Additional Information

I just noticed that if you re-trigger the build_marts task a second time (after rxnorm has run once automatically when you turn it "on" and once triggered by build_marts)... it will not RE-trigger rxnorm a third time. It seems to be satisfied by its own triggering of the DAG and run to completion. Could there be a difference between the types of triggers of the tasks? What is satisfying it the second time around?