Pipes to be wired in after all other strategies. The pipe's launchJob()
implementation should wait on the downstream strategy's launchJob(). This
has the effect of respecting the constraints of concurrency, rate-limits
and other strategies configured by built-in NevermoreOptions. However,
it means that your pipe can add its own additional scheduling, job behaviours
or annotations. See createPassthruPipe for a reference code to build your
own strategies.
Pass this option to chain custom strategies after the built-in strategies.