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.
- If the user could not submit the item for publishing
If the Publishing Queue does not list the item being published at all, this means that the item was never submitted for publishing. - If the Publishing Queue shows Success but you do not see it on the website
A status of Success in the Publishing Queue means that either the wrong thing was published, or it was published to the wrong place. - If the Publishing Queue shows 'Success' but you see stale content on the website
Stale content may point to a workflow problem or a caching problem. Note that unpublished content that remains visible on the website is also stale content. - If the Publishing Queue shows the item stuck at Scheduled for Publish
The 'Scheduled for Publish' message means that the user who submitted the item for publishing explicitly set a date and time at which Content Manager should start generating publishable content (rendering). The item stays in this state until that date and time. - If the Publishing Queue shows the item stuck at Waiting for Publish
The 'Waiting for Publish' message means that the publish transaction is stuck in the Publisher Queue. If this problem does not resolve itself over a short period of time, consider what might be causing a heavy load. - If the Publishing Queue shows the item stuck at In Progress
The 'In Progress' message means that the publish transaction is stuck in the Publisher Service. If this problem does not resolve itself over a short period of time, your code may be causing the Publisher to hang, or its load may be too heavy. - If the Publishing Queue shows the item stuck at Scheduled for Deployment
The 'Scheduled for Deployment' message means that the user who submitted the item for publishing explicitly set a date and time at which Content Manager should start placing content online (deploying). The item stays in this state until that date and time. - 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. - If the Publishing Queue shows a status of Deploying but the publish action shows up as finished
If the Published to tab of the Where Used dialog for an item shows it as having been published successfully, but the Publishing Queue still shows a status of Deploying and the published item does not appear correctly, try changing the read timeout (Oracle) or socket timeout (Microsoft SQL Server) setting on the server. - If the Publishing Queue shows a status of Warning
The 'Warning' status means that the user configured a number of render errors to ignore, and one or more rendering errors occurred. If the setting was set correctly, this is not a problem. - If the Publishing Queue shows a status of Failure
A 'Failure' status in the Publishing Queue indicates that somewhere in the publishing pipeline, an error occurred that prevented the item from being published. Find out more details about the failure by double-clicking the item in the Publishing Queue.