Documentation Center

If the Publishing Queue shows the item stuck at Waiting for Deployment

The 'Waiting for Deployment' message means that the item is waiting to be deployed, and is currently in the Content Deployer queue.

This typically happens if either your maximum file size or your maximum request size, as configured in the Content Deployer application.properties file, has a value that is too low. The settings are called spring.http.multipart.max-file-size and spring.http.multipart.max-request-size, respectively.

Normally, a "Waiting for Deployment" message simply means that Content Deployer is temporarily overwhelmed, and that deployment will occur with an acceptable delay. But if you see many items in this state, or if you see the same item stuck in this state for an unacceptably long time, too many items are being sent to the Content Deployer.

To resolve a persistent Waiting for Deployment state, do one of the following:
  • Increase the number of workers. This increases CPU load and may require a hardware upgrade (more CPU cores).
  • Decrease the total number of Publisher threads (configured as the TransportPriorityPoolSize attribute of the Workers element) in the Transport Service, cd_transport_conf.xml.