3.1.5.4.21 PIPELINE_STATE Message

The syntax of this message is specified in section 2.2.2.21.

A server sends this message to a RunspacePool or pipeline on the client.

The client SHOULD ignore PIPELINE_STATE messages targeted to RunspacePools.

If this message is targeted to a pipeline, the server sends a message to notify a client about the pipeline's state. After this message is received, the client extracts the state information (section 2.2.3.4) from the message and updates the pipeline state (section 3.1.1.3.2) accordingly. Once a pipeline reaches a Completed or Failed or Stopped state (section 3.1.1.3.2), the client MUST remove the pipeline from the corresponding RunspacePool's pipeline table (section 3.1.1.2.6) and the global pipeline table (section 3.1.1.1.2).

If this message is targeted to a pipeline, the client's pipeline MUST be in a Running state (section 3.1.1.3.2) while processing this message. If the pipeline is not in a Running state, the client SHOULD ignore this message.

The details of how a client executes a pipeline on a server are specified in section 3.1.4.2.