Job's referenced from via JobRef don't have their statistic's updated

deferring for future release..

from irclog:

gschueler

3:42 well the problem is that when you run a jobref, it doesn't really run the job..it just runs the workflow for the job

3:43 i.e. there is no "Execution" associated with that job

noahcampbell

3:43 We can bump this out to a later revision

3:44 I just noticed that a particular job of significance was being called many many times through a jobref and there were no job stats. This makes it look like it's not being used

gschueler

3:45 ok…i think we'd either have to modify Execution to allow some kind of chained Execution (which has no output file of its own), or update the way stats are calculated so that the successrate is stored in the ScheduledExecution

3:45 right now it just queries for number of successful Executions