Issue was that the initiating GATK query was triggered by any Ubam node. With 0.5.2, all relationships are added via triggers, and the OUTPUT relationship (i.e. (fastq-to-ubam)-[OUTPUT]->(Ubam)) returns the Ubam node and sends it to be checked for triggers. This means that the ubam is sent to the trigger function twice; 1) when the node is created and 2) when the OUTPUT relationship is added. Hence, job queries were being triggered twice.
Current fix is to add required header labels to the trigger, so that it is only activated after the relationship has been added, as opposed to after the node is created.
Issue was that the initiating GATK query was triggered by any Ubam node. With 0.5.2, all relationships are added via triggers, and the OUTPUT relationship (i.e. (fastq-to-ubam)-[OUTPUT]->(Ubam)) returns the Ubam node and sends it to be checked for triggers. This means that the ubam is sent to the trigger function twice; 1) when the node is created and 2) when the OUTPUT relationship is added. Hence, job queries were being triggered twice.
Current fix is to add required header labels to the trigger, so that it is only activated after the relationship has been added, as opposed to after the node is created.