If the Publishing Queue shows the item stuck at Throttled

The 'Throttled' state indicates that the Transport Service are sending more Transport Packages than the Content Deployer can handle. This may be a temporary problem that resolves itself in some 10-20 minutes, but if it persists, you may have to change your configuration.

A 'Throttled' state indicates that the total number of Publisher threads in use by all Publishers exceeds the total number of Content Deployer threads, configured as the Deployer's window size and workers in the Content Deployer configuration file. Items in a Throttled state are put on hold on the Content Manager side and retried after a certain (slowly growing) interval.

To resolve a persistent Throttled state, do one of the following:

  • Increase the number of workers (configured as the Workers attribute of the Location elements) in the Content Deployer configuration file, cd_deployer_conf.xml. This increases CPU load and may require a hardware upgrade (more CPU cores).
  • Increase the window size (configured as the WindowSize attribute of the Location elements) in the Content Deployer configuration file. This makes deployment of content slower because items now have to wait in the Content Deployer queue.
  • Decrease the total number of Publisher threads (configured as the TransportPriorityPoolSize attribute of the Workers element) in the Transport Service, cd_transport_conf.xml.