Multiplexed outputs are ignored if they don't have matching inputs. If there is only one task in a workflow, then there are no inputs to be matched to. This means a single multiplexed task's outputs cannot be accessed.
Several users have tried to use the 'RDA_Materialization' task by itself. Since this task is multiplexed, the resulting image file is ignored as an output and can not save. There is also the RDA_Materialization_Simple task that is not multiplexed, but the distinction between the two tasks is not evident unless the user compares the task definitions.
This skips the output matching if there is only one task.
Ideally, unmatched multiplex outputs should only be ignored if there is one or more matching inputs on the next task. This would let any multiplex task that is at the "end of the line" have accessible outputs. However, this problem has not been reported by users yet.
drwelby
commented
5 years ago
Multiplexed outputs are ignored if they don't have matching inputs. If there is only one task in a workflow, then there are no inputs to be matched to. This means a single multiplexed task's outputs cannot be accessed.
Several users have tried to use the 'RDA_Materialization' task by itself. Since this task is multiplexed, the resulting image file is ignored as an output and can not save. There is also the
RDA_Materialization_Simpletask that is not multiplexed, but the distinction between the two tasks is not evident unless the user compares the task definitions.This skips the output matching if there is only one task.
Ideally, unmatched multiplex outputs should only be ignored if there is one or more matching inputs on the next task. This would let any multiplex task that is at the "end of the line" have accessible outputs. However, this problem has not been reported by users yet.