Job(s) Retry Queue
This submodule displays details of upload jobs that have been re-executed (re-run) from the upload jobs module.
The module ensures that jobs are eventually completed while providing transparency on job statuses, such as who initiated the task, where it was triggered, and its current progress.
What you see on the screen
In this section, users can only view the listed fields; no actions can be performed.
Label
Description/ Example
Triggered By
Displays the name of the user who initiated the upload job.
Triggered From
Shows the device's IP address from which the upload job was triggered.
Job Type
Specifies the type of upload job (e.g., Upload Job Task Retry).
Job Name
Shows the name of the upload job.
Execution Identifier
Displays a unique code that identifies the execution of the job.
Re-Run All Devices
The field is available for review but without actionable items.
Status
Indicates whether the job is "Waiting for Execution" or "In Progress."
Creation Time
Displays the date and time when the job was created.
MSP-Based Visibility
MSP support in Job(s) Retry Queue ensures retry job entries are visible only within the user’s MSP scope.
When MSP is enabled, retry jobs are filtered based on Customer or Entity mapping. When MSP is disabled, retry jobs follow organization-level visibility rules.
Customer User
Can view retry jobs only for assets mapped to their Customer.
Visibility follows organization-level access. No MSP filtering applied.
Entity User
Can view retry jobs only for assets mapped to their Entity.
Visibility follows organization-level access. No MSP filtering applied.
Organization User
Can view retry jobs for all assets within the organization.
Can view retry jobs for all assets within the organization.
Data Filtering
Retry jobs are filtered based on Job → Asset → MSP mapping.
No MSP-based filtering.
Last updated