Publishing Queue (Beta)

The Publishing Queue (Beta) is an updated version of the Publishing Queue tool, rebuilt on Angular as part of dotCMS's UI modernization. It presents all bundles in a single unified table filtered by status, replacing the older two-column layout with a more streamlined view.

To access it, see the Beta Activation section.

Beta Activation#


As a beta feature, the new Publishing Queue must be manually added to a tool group. For general information on tool groups and adding or removing tools, see Roles and Tools.

Within the Roles & Tools Settings tool, simply add the Publishing Queue (Beta) to your chosen group — in this case, Site Manager.

Adding the beta Publishing Queue tool.

Then go to Site Manager → Publishing Queue (Beta) in the navigation bar.

The Bundle List#


The main view displays all publishing bundles in a single table. Clicking a bundle's name opens the Bundle Details modal directly.

Screenshot of the Publishing Queue (Beta) main list view.

Columns#

ColumnDescription
Bundle NameThe bundle name. Auto-generated bundles use a timestamp format (bundle-YYYY-MM-DD HH:MM:SS). Click to open Bundle Details.
Bundle IDThe bundle's unique identifier. Hover the row to reveal a copy button.
FilterThe push publishing filter applied when the bundle was created — for example, Everything and Dependencies.
ItemsThe number of assets in the bundle.
Date EnteredWhen the bundle was added to the queue.
Last UpdateWhen the bundle's status last changed, shown as relative time.
StatusThe bundle's current state. See Bundle Statuses.

Bundle Statuses#

StatusMeaning
ScheduledThe bundle has a future publish date and is waiting for that time to arrive.
Bundle RequestedA push has been requested; the system is preparing the bundle.
Waiting for PublishingThe bundle is assembled and waiting for a publishing slot.
BundlingAssets are being packaged.
Sending to EndpointsThe bundle is being transmitted to one or more receiving endpoints.
Publishing BundleThe receiving endpoint is unpacking and applying the bundle.
Received BundleThe endpoint has received the bundle.
SuccessThe bundle was published successfully to all endpoints.
Failed to Send to All GroupsTransmission failed for every endpoint group.
Failed to Send to Some GroupsTransmission succeeded for some endpoint groups but not all.
Failed to BundleThe packaging step failed.
Failed to SentSending failed after the bundle was dispatched.
Failed to PublishThe receiving endpoint could not apply the bundle.
Failed Integrity CheckThe bundle failed a content integrity check on the receiver.
Invalid TokenAuthentication with the receiving endpoint failed.
License RequiredThe receiving instance does not have the required license.

Toolbar#


The toolbar above the table provides search, filtering, refresh, and bundle management controls.

Screenshot of the Publishing Queue (Beta) status filter.

The search field filters the list by bundle name. Results update as you type.

Filter by Status#

The Filter by Status dropdown narrows the list to bundles in one or more specific states. Select any combination of the 16 available statuses; the table updates immediately. The dropdown includes a search field for quickly finding a specific status.

Refresh#

The Refresh button reloads the bundle list from the server without a full page refresh. Use it to check for status changes on in-progress bundles.

Bulk Actions#


Selecting one or more bundles via their row checkboxes replaces the Add Bundle button in the toolbar with two bulk action buttons.

Screenshot of the toolbar with two bundles selected, showing Remove and Retry Send.

ActionBehavior
RemoveDeletes all selected bundles from the queue. This action is permanent.
Retry SendRe-queues all selected bundles for another push attempt. Useful for recovering from transient failures like Failed to Send to All Groups.

Adding a Bundle#


The Add Bundle button in the top-right corner has two options: Select Bundle and Upload.

Screenshot of Add Bundle with its dropdown visible.

Select a Saved Bundle#

Add Bundle → Select Bundle opens a two-panel dialog. The left panel lists bundles that have been created and saved for later rather than pushed immediately. Use the search field to locate a specific bundle. Selecting a bundle in the left panel shows a preview of its contents in the right panel.

From this dialog you can:

  • Remove — delete the selected saved bundle.
  • Download — download the bundle archive.
  • Configure — open the bundle in the standard push-publishing dialog to set the target environment and schedule the push.

Screenshot of the Select Bundle dialog.

Upload a Bundle File#

Add Bundle → Upload lets you add a bundle that was generated externally. Drag the file onto the drop zone, or click choose a file to browse. Accepted formats: .tar.gz and .tgz.

This is useful for pushing content between environments when direct server-to-server publishing is not available — for example, transferring a bundle from a staging instance to a production environment by file.

Screenshot of the Upload Bundle dialog.

Row Actions#


Hovering over any row reveals a menu on the right with four actions. The same radial menu can be accessed by right-clicking on any bundle.

Screenshot of the row action menu.

Screenshot of the right-click menu.

View Details#

Opens the Bundle Details modal. This is also triggered by clicking the bundle's name in the table.

Screenshot of the Bundle Details modal.

The modal shows the bundle's full metadata:

FieldDescription
Bundle detailsThe bundle name and total asset count.
StatusCurrent bundle status.
Bundle IDThe bundle's unique identifier.
Bundle startThe scheduled start of the bundle window, if set.
Bundle endThe scheduled end of the bundle window, if set.
Publish startWhen publishing began.
Publish endWhen publishing completed.
FilterThe push publishing filter used.
Total assetsNumber of assets included.

The Endpoints table shows every receiving endpoint the bundle was sent to, with per-endpoint status and the status message returned by the receiver (for example, Everything ok).

Footer actions:

  • Download Manifest — downloads a text file listing every asset in the bundle.
  • Download — downloads the full bundle archive.

View Contents#

Opens a modal listing every asset in the bundle, with each asset's Name and Type (for example, contentlet).

Screenshot of the View Contents modal.

Generate / Download#

Opens a dialog for regenerating and downloading the bundle archive.

Screenshot of the Generate / Download dialog.

Choose whether the bundle should be generated for a Publish or Unpublish operation, then select the Push Publishing Filter to apply. Click Download to generate and download the archive. Use this when you need a bundle file for manual transfer or to re-generate with different settings, without going through the Bundle Details modal.

A toast message will announce the success of the process.

Screenshot of the toast message on successful generation of a downloadable bundle.

Delete#

Permanently removes the bundle from the queue.

Pagination#


The bundle list is paginated. Use the page controls at the bottom of the table to navigate between pages. The rows-per-page selector (default: 20) controls how many bundles appear per page.

Screenshot of Publishing Queue (Beta) pagination.