Idea Delivered

Web UI Publish Queue - Delete multiple events

In the Web InfoShare, we need to be able to delete multiple stalled publish events. Currently, in TD 14 SP3, we can only select one event at the time. 

  1. Go to Event Log > Publish, and select Show Busy, for example.
  2. If multiple publications have failed these will be listed and will clog the view.
  3. Provide an option to do a multiple selection before you click Delete, or an advanced Delete 
Tatyana Morkot

  • Hi all, 

    I wanted to share an update about the Events page. In the upcoming version of Tridion Docs 15.2, we’re refreshing the user interface for the Events pages. This update will make it more usable to take action directly from the Events Overview, and it will be more clear how to use the multi-select feature for deleting items.

    A preview of the new design: 

    Screenshot of Tridion Docs Events Overview page showing a refreshed user interface. The left panel lists filters and event groups, while the main panel displays a table of events with columns for User ID, Event ID, Description, Date Created, Date Modified, Status, and Progress. One event shows a warning status.

    Best, 

    Gizem

  • Hi all,

    I hope I can give some quick background on the below helpful answers,

    Event Log by itself is a centralized 'logging' system, so on top of logging onto the file system in every server of your scaled out environment. This way many users (if not all users) get visibility on what is technically happening on the various servers. It is however still a logging system, some people see Event Log as "the queue" which is technically incorrect. Regarding clean up of busy events, please have a look at Standard SQL Server Database Job - RWS Documentation. Of course if you are automating publishing - and in turn cancelling - you can also automate the clean up of your event when cancelling using the API.

    "The queue" is called BackgroundTask but even then it is not a single queue. It is a complex matrix of small (executed in seconds) to large messages (taking 12+ hours to execute). Handlers, servers hosting handlers and grouping handlers to achieve fairness and throughput - even upon retries. Most handlers are fire-and-forget meaning that you cannot really stop them from executing (unless you use the operating system's process id to kill the process), upon several failures as configured in settings background task xml they will stop. Some handlers like "publish", have several check points to verify if the requested publish operation is not cancelled (so Cancel of a Publish of a PublicationOutput). See Admin.XMLBackgroundTaskConfiguration.xml - RWS Documentation or Background task component - RWS Documentation for more info

    -Dave

  • in reply to Elizabeth Gschwind

    Hi Elizabeth, my question was related to tidying up after multiple failed events. The processes would be either stalled or failed on the server. 

    We publish using some automated scripts that will cancel publishing if it runs for too long. The event on the other hand will remain in the Publishing Queue in the Web InfoShare.

  • in reply to Roy Janssen

    Thanks. One of my colleagues did suggest I do this! Should have asked them in the first place. 

  • in reply to Elizabeth Gschwind

    That's not how I understood the question.
    Stopping an event on the server is possible by an administrator.

    1. Open an event in the event log and find the Process ID. 
    2. log in to the server that is handling the job. 
    3. In the task manager make the column PID visible.
    4. Search for the Process ID and kill the job.