Publish transaction states
A publish state indicates the stage in the publish transaction. You can view the publish state of a publish transaction by viewing the Publishing Queue.
A publish transaction is an individual package that is being published. One publish action, (for example, republishing a Component) may result in several publish transactions if the publish action results in the Component being published on more than one Page.
State flow diagram
The following diagram provides an overview of the publishing states:
The state of a publish transaction is based on the stage in the publishing process that has started. The state changes whenever the publish transaction is scheduled, put in the message queue, is in progress by the publisher, or is finished/failed. The flow is slightly different depending on whether the publish transaction is scheduled in the future versus requested to be done immediately.
Publishing flow when scheduled
The following table shows the stage of the publish transaction and the corresponding state when the publish time is scheduled.| Step | Description | Publish transaction state |
|---|---|---|
| 1 | A User publishes an item. The Content Manager creates a Publish Transaction for each combination of Publication and Target Type. The Content Manager schedules the publish action. | Scheduled |
| 2 | The scheduled render time arrives. The Content Manager sends the item to the Publisher. | Waiting for publish |
| 3 | The publisher picks up the publish transaction from the queue and renders and resolves the items. | In progress |
| 4 | The transport service sends the rendered information and metadata to the Content Deployer with a wait command. | Waiting |
| 5 | The deploy command is scheduled. | Scheduled for deployment |
| 6 | The scheduled deploy time arrives. | Waiting for deployment |
| 7 | The publisher retrieves the publish transaction from the queue. | In progress |
| 8 | The Transport Service sends rendered information and metadata to the Content Deployer with a Deploy command. | If the transport is not successful, the status is set to If the transport is successful, but errors occurred while generating publishable content, the status is set to If the transport is successful, the status remains |
| 9 | If the transport was successful, the Content Deployer deploys the content. | If the deploy is successful, the status is Success. If the deploy is not successful, the status is Failed. |
Publishing flow when immediate
| Step | Description | Publish transaction state |
|---|---|---|
| 1 | A User publishes an item. The Content Manager creates a Publish Transaction for each combination of Publication and Target Type. | Waiting for publish |
| 2 | The publisher picks up the publish transaction from the queue and renders and resolves the item. | In Progress |
| 3 | The Transport service sends rendered information and metadata to the Content Deployer with a Deploy command. | If the transport is not successful, the status is set to If the transport is successful, but errors occurred while generating publishable content, the status is set to If the transport is successful, the status remains |
| 4 | The Content Deployer deploys the content. | If the deploy is not successful, the status is Failed. |