For each notification in the source sequence, CreateObservable constructs a new instance of the asynchronous operation specified in the nested workflow and emits the operation exposed as an observable sequence. However, CreateObservable does not itself subscribe to the sequence, which means the logic inside the nested workflow will not run unless the emitted observables are subscribed downstream.

Note

You can manipulate and schedule each of the emitted observable sequences downstream using higher-order operators such as Merge, Concat or Switch.

The input to the nested workflow represents the element passed as an argument to the asynchronous operation. If the input is itself an observable sequence, the WorkflowInput node will subscribe to all the values in the sequence when the asynchronous operation is finally launched. Otherwise, the input will emit a single value containing the stored argument value.