In the CME, failed publishing requests are replaced by newer publishing requests that succeed.
Can we somehow see the failure details later?
I agree with JanH's point that the queue isn't a logging mechanism. So I’m thinking we should check logs depending on where the transport package failed, review the troubleshooting list in the documentation, and maybe log some details with the event system.
- No item in the queue means nothing was submitted.
Successbut not on website suggests wrong item or wrong place.
Successbut stale content on website might be workflow, caching, or multiple Content Deployers.
- Stuck in
Scheduled for Publishmay simply be a scheduled item.
Waiting for Publishshould go away normally, but consider what's causing load.
In Progressmeans Publisher Service. It's either load or code.
Waiting for Deploymentsimply means the item is in queue. (Keep pressing that refresh icon). :-)
Transport Serviceis sending more
Transport Packagesthan the
Content Deployercan handle. Wait up to 20 minutes or so and then check configuration.
Warningmeans the user chose to ignore render errors, but render errors occured. Not a problem if expected.
Failuremeans an error occured in the publishing pipeline that prevented the item from being published. Double-click the item in the Publishing Queue to learn more.
When describing a logging approach, I think we'd use the Event System to subscribe to the
TransactionCommitted?). Anyone have an example of what we'd need in the handler? I'm sure we need to handle publishing and unpublishing, anything else and where would you save this information?