Troubleshooting publishing
This section explains ways to resolve publishing problems.
- Publishing states
In the user interface, the Publishing Queue shows the status, or state, of each publish transaction, which indicates the stage in the publish transaction. - Transport Packages
Depending on the nature of the publish (or unpublish) action, one or more Transport Packages are created on the Content Manager side. The Transport Packages that are sent to the Content Deployer can help you determine where a publish action went wrong. - Capturing transport packages for analysis
By default, the Content Deployer is configured to clean up incoming transport packages after a certain period of time. When studying a publish problem, it can prove useful to disable this cleanup in order to be able to capture and study these packages. - Locating where publishing fails
A number of problems along the publishing pipeline can cause publishing to fail, slow down, or not produce the desired output. This section helps you zoom in on the location in the pipeline causing the problem and solve the problem. - Troubleshooting scaled-out publishing
This topic describes how the publishing pipeline may be scaled out, and the specific publishing issues that can arise as a result. - Transport Service and Content Deployer logs
Both the log files and the configuration files of the Transport Service and the Content Deployer can help you zoom in on publishing problems. Configure and analyze your log files to zoom in on publishing problems related to the Transport Service or Content Deployer.