logo
logo

Current activity

The Current activity tab shows the activity in your Sitecore Content Hub instance. You access it from the Stats page.

Information is grouped into two sections:

  • Queue: shows the number of messages that are on each of the processing queues.
  • Jobs: shows the results of the processing jobs.

Queue

For each type of job, Content Hub sends one or more messages as a form of communication between two elements. Messages contain the data needed by the workers assigned to each queue to fulfill the job assignment.

When a new message is created, it becomes visible in the IN stage of the queue. While the message is being processed, it is visible in the WIP (Work In Progress) stage. When processing has been successfully completed, the message is visible in the COMPLETE stage. If a message cannot be processed, it is visible in the DEAD stage. You can find additional information regarding the failure in the server logs.

Note

Using Content Hub, you can set up message prioritization where priority values are set on job types and media types. For example, processing image files can have a higher priority than video files, so they are processed first.

Description of queues

The following table lists all the queues in Content Hub:

QueueDescriptionScalable
actionsApplies to actions invoked either through triggers or manually, through the API.Yes
assetlifecyleOptimizes storage for files located in the Azure Blob storage of an asset, whether it is archived or not.No
auditLogs and saves activities in an Elasticsearch audit log index.No
businesslogicRuns configurable logic when certain system events occur, and is mainly used with Sitecore Marketing Resource Management (MRM).No
checkoutUsed to move the selected assets to OneDrive.No
chili_validationValidates the uploaded Chili templates and can be used for Chili integration.No
cleanupUsed for cleaning up entities that are no longer required. If one entity is linked to files (such as a file entity), those files are also deleted.No
compositeassetsFilters Save entity messages from a configured list of definitions and starts a worker to handle them. It looks for newly uploaded archive files that match a configured file pattern and creates processing jobs for them. Finally, it extracts specific files from the archive and adds them to the file entity that represents the archive.No
connectorpublishingPublishes data from connectors.No
discussionnotificationSends notifications to users when they are mentioned in discussions or comments.No
download_reporting_logsCreates a download package when the user requests the download of reporting logs.No
download_script_telemetryCreates a download package when the user requests the download of script telemetry logs.No
drmcomplexityForces assets to require explicit approval by updating the ExplicitApproval Required flag and associated digital rights management (DRM) properties.No
duplicatefileChecks for duplicate files, creates FileDuplicate entities for each duplicate type, and flags duplicate assets as HasDuplicate: True.No
entitypublishingPublishes entities to Edge.No
exportdataProcesses data exports. It is used both for exporting to Excel and for exporting translations.No
fetchLets users upload assets from either a UNC path or a public URL. The newly uploaded assets are then added as file entities to an existing asset entity. However, it must wait for a copy operation to finish before starting the next job.Yes
flowForwards incoming messages to the flow queues that match the message channel. Only one instance of this worker is permitted.No
flow-allDeals with media processing messages.No
graphProvides a gateway for the Graph server, which is a service with in-memory graph representation of all data in the Content Hub instance. The Graph server provides a bridge between normalized data in the Redis data storage and de-normalized data in the Elasticsearch data storage.No
high_priority_fetchSimilar to the default fetch queue, except that it processes high-priority jobs.Yes
high_priority_import_dataSimilar to the default importdata queue, except that it processes high-priority jobs.No
import-renditions-metadataContains a single message for each M.File entity. This message is processed and the results are written back to the M.File entity.Yes
importdataProcesses data imports. It is used to import Excel files, mass edits, and translations.No
masseditLets users make multiple edits for all selected entities. It can be configured to exclude relations and properties from the assets.No
orderingPrepares download orders by converting and archiving files, as requested by users.No
packageDeals with requests for exporting and importing packages.No
processingDeals with processing jobs based on a priority queue.Yes
publiccollectionUsers who have the manager role for a collection, as well as the PublishCollection privilege, can make that collection public, making all its assets available through an external website. Access to this external website can be configured to require authentication.No
publiclinkUpdates the state of the public link entities in an Azure table.Yes
publisherActs as the entry point for all messages. Every message goes through the publisher queue before being propagated.No
renditionsBased on a specific configuration, it scans a queue of saved entities, detects property changes, and sets up a processing job.No
rolesUpdates the user group policies when creating, updating, or deleting a role template.No
scriptcompilationBuilds requested scripts in C#.Yes
sendemailSends email messages.Yes
sitecore_machine_learningSends information about assets to the Sitecore AI, which processes similarity metrics for specific assets.No
systemDeals with large, time-consuming system jobs that are executed after an upgrade. These jobs are excluded from the upgrade process itself, but begin when the system is live. Examples are translation updates, theme refresh, or large entity updates.No
tasknotificationSends email notifications to users during the following situations:
  • At the creation of an M.Project task, to notify the assignees.
  • At the completion of an M.Project task, to notify the task creator.
  • When the creator of a M.Project task wants to send a reminder to the assignees.
No
tasksCopies an M.Project task and assigns it to specifics users.No
themeGenerates themes based on data in a theme entity.No
themenotificationNotifies Media Delivery when it has to refresh the cached theme.No
totalfilesizeSets the properties TotalColdFileSize and TotalHotFileSize on all existing file entities in the system. Depending on the number of assets and files already archived, this can take several hours.No
triggersWhenever there are changes in the system, it checks if the trigger conditions are met and, if so, it activates the trigger.Yes
uploadAdds a new Add links button to the Create page, letting users create assets based on files from an external source.Yes

Jobs

The Jobs section lists the jobs available in the system along with the current state of the job. If a job fails, an entity could have no renditions for example. You can investigate failed jobs on the My Jobs page.

Note

Each user can access the jobs they created from their personal Background processes page.

Can we improve this article ? Provide feedback