Viewing the Publishing Queue

The Sitecore XM Cloud publishing queue displays all active and recently processed publishing jobs within a Sitecore environment (i.e., MSU-Green/Prod) from all users across campus. This tool can also be used to cancel a user’s own publishing request.

Access the Publishing Queue

  1. Log into Sitecore XM Cloud.
  2. Click the desired environment to view its publishing log. (e.g., MSU-Green/Prod or MSU-White/Prod)
  3. Click Open app in the menu on the right.
  4. Click Settings on the navigation menu at the top of the page.
  5. Click Publishing jobs in the menu on the left.

Using the Publishing Queue

The Publishing jobs page shows active and recent publishing jobs in the environment. The list can be filtered by Status, Triggered on (date of publishing request) and Triggered by (user making the request). 

The Status column indicates the number of items or components published (indicating changes were made) or skipped (no change or publishing required).

The Information icon (“i”) in the last column indicated additional data available. Click this icon to view details of the publishing job, including publishing options, the duration the job was in the queue (waiting to be published) and the duration the job was running (actively being published).

Addressing Publishing Delays

Publishing duration is typically between 40 seconds and two minutes. Longer publishing durations may indicate a situation where a page was published using the “Subpages” or “Related Items” options. These jobs may take 45 minutes or more.

If a long-running job is causing the publish queue to back up with waiting jobs, contact the University Communications and Marketing Platforms group with details.

Users can terminate their own publishing job by clicking the Cancel Job icon (red circle with a line) at the right end of the row for the specific publishing job. General users can only cancel their own jobs. Sitecore administrators can cancel any publishing job.

 

 

Documentation updated: September 30, 2025

Is there an issue with this documentation? Report it here.