Right now, when a FW has
as a spec key, the FW name, FW ID and FW launch directory from the parent job passed.
Normally, the FW’s state is redundant, as it should be “COMPLETED” for the child FW to run — unless the FW also has the following as a spec key:
In this case, the child can run if some or all of the parents are “FIZZLED”
It would be useful in such a case to add the FW’s state when using “_pass_job_info”
This is an easy fix, and I have submitted a pull request for it: