Changing the state of a channel immediately changes its state on all nodes in the cluster. For example, when you deploy a channel in the Mirth® Connect Administrator, the channel immediately deploys across the cluster. The same principle applies to starting/stopping/pausing/resuming/halting channels. This ensures that the state of your channels is consistent on all servers in the cluster.
Note: When you change a channel state, the state may temporarily appear as Syncing while the command is processed across the cluster. If the channel state remains stuck as Syncing, an error may have occurred on one or more servers, which kept the channel state operation from completing. If such an error occurs, use the Cluster Task History tab to diagnose the problem. (See the Cluster Task History Tab section below.) To clear the Syncing status, you may need to halt and redeploy the channel.
