Job queue
Monitor records pending dispatch to channels and scheduled PIM jobs, and run a job immediately if needed.
Job queue screen shows two things that PIM runs in the background in one place: Pending dispatches not yet sent to channels (such as website and search integrations) and Scheduled jobs that run at specific intervals. Use this screen to understand why a product change has not yet reflected in a channel, notice dispatch backlogs, and run a scheduled job immediately if necessary.
Accessing the screen
- Follow the path PIM & Catalog › Operations › Job queue in the left menu.
If you do not see it in the menu, your account does not have permission for this screen. Viewing jobs and running jobs are separate permissions: if you lack run permission, you can only watch the screen.
Screen sections
- Header: Job queue with the description "Pending integration dispatches and scheduled jobs." below; Refresh button on the right. Refresh is disabled while data is loading.
- Warning stripe: "Pending dispatch query scans the entire product collection; auto-refresh is off."
- Pending dispatches table.
- Scheduled jobs table.
Data loads once when the screen opens and does not refresh automatically. Because calculating pending dispatches is a heavy query, press Refresh to see the current status. Numbers may remain the same for a short time (about 15 seconds) on consecutive refreshes; pending dispatch results are shown without recalculation during this period.
Pending dispatches
This table shows product records waiting to be sent to channels as a three-level tree: Integration › Request type › Parameter.
| Column | Meaning |
|---|---|
| Integration / Request type / Parameter | Tree node. Top rows are integrations (bold, gray background). Below are request types for that integration, and at the bottom is the integration parameter number. Integration and request type are shown by their system codes. Levels without values appear as "—". |
| Qty | Total number of pending records under that node. The upper node's count is the sum of its child nodes. |
| Oldest | Time of the oldest pending record in the node. |
| Newest | Time of the newest pending record in the node. |
- Integrations are collapsed by default. Click the + / − button left of the name to expand or collapse a node.
- The Expand all button at the top right of the table opens all nodes; when all are open, the button changes to Collapse all.
- Rows at the same level are sorted by quantity descending (if quantities are equal, by name): the integration with the most backlog is at the top.
- If no pending records exist, the table is replaced by "No pending dispatches: all channels are up to date."
If the Oldest time goes far back, dispatches may not be progressing for that integration. If Oldest does not change after several refreshes, report the situation to the integration responsible.
Scheduled jobs
This table lists jobs that PIM runs at intervals and that you can manually trigger.
| Column | Meaning |
|---|---|
| Job | Job name; short description if available below. |
| Status | Current status of the job (see table below). |
| Last start | Last time the job started. "—" if never run. |
| Cron | Expression defining the job schedule (in cron format; e.g., daily at a specific time or at certain minute intervals). |
| Run | Play button that triggers the job immediately; shows Run on hover. This column is visible only if you have job trigger permission. |
Statuses
| Status (on screen) | Meaning | Next step |
|---|---|---|
| Running | Job is currently running (blue badge). | Wait for it to finish; do not retrigger. |
| Pending | Job is queued to run (yellow badge). | Press Refresh after a few seconds. |
| Idle | Job is active but not running now; will run when scheduled (green badge). | Trigger immediately with Run if needed. |
| Frozen | Job is inactive (gray badge). | Do not expect it to run automatically; ask your administrator. |
Unknown statuses are shown with a gray badge.
Operations
Running a scheduled job immediately
Use this to run a job without waiting for its next scheduled time.
- Click the play button (Run) in the row of the desired job in the Scheduled jobs table.
- The Trigger this job now? box opens; the job name is shown under the heading.
- Read the note: the job is queued immediately, the result is not awaited, and triggering cannot be undone.
- Click Run. To cancel, click Cancel. While sending the request, the button shows Loading and the box cannot be closed.
Result: "Job triggered" notification appears and the list refreshes. The screen does not wait for the job to finish; the job status updates in the table within seconds. Press Refresh to see the latest status. If triggering fails, a red error notification appears and the box remains open.
Additional warning for Cache jobs
When running a job with "Cache" in its name, the box checks if there are pending records not yet transferred to web or search infrastructure (Elastic):
- If there are pending records for web or Elastic integration in the Pending dispatches table, the box shows "There are pending records not yet transferred to Web or Elastic. If cache is refreshed now, these changes will not be reflected." warning.
- If pending dispatches could not be read, a warning states it is unknown whether such records exist and cache refresh may not reflect them.
- In both cases, the Run button turns red. The check is based on the currently loaded table; if the table is outdated, press Refresh first.
When you see this warning, the best approach is to wait for all pending dispatches to complete, check the table with Refresh, then run the cache job. You can proceed despite the warning, but pending changes will not be reflected in this cache refresh.
Common situations
- No play button or Run column. Your account lacks job trigger permission; a note appears below the table. You can only view the list.
- "Pending dispatches could not be read now; scheduled jobs are below." The pending dispatch query failed this time; scheduled jobs are still listed. Try Refresh later.
- My product change did not reflect in the channel. Open the relevant integration in the Pending dispatches table and check for pending records. If records are pending, dispatch is queued; if none, check the result in Operations and Dispatch logs screens.
- I triggered a job but its status did not change. Triggering queues the job without waiting for the result. Press Refresh after a few seconds; if the job still shows Idle, check if the Last start time has updated.
- "Something went wrong" error appears. Retry with Retry; if the problem persists, send the text in the Technical detail section to your system administrator.
Related screens
- Operations — log of bulk product operations and dispatch results.
- Dispatch logs — records of product dispatches to channels.
- Bulk product dispatch — manually resend selected barcodes to sales channels.
- Overview — general overview of PIM & Catalog screens.