3.2.1.3.2 Pipeline State

Each pipeline has an associated state.

Section 2.2.3.5 lists available states and describes the data type used to encode the state in PSRP messages.

For details about how a pipeline state transitions from NotStarted to Running, see section 3.2.5.4.10.

The server can change the pipeline state from Running to Failed at any time if it determines that there is something wrong with the pipeline (such as a network connection getting lost, a corrupted RunspacePool is in bad state, or a pipeline failed while executing). After changing the pipeline state to Failed, the server MUST send a PIPELINE_STATE message (section 3.2.5.4.21) with a Failed state to the client.

When the pipeline state is changed to Completed, Stopped, or Failed, the server MUST NOT send any PSRP messages to the client targeted to that particular pipeline.

Figure 5: Server pipeline states and transitions