Skip to main content
Long-running and batch operations in MerchantOps run as jobs. A job groups many items into one tracked operation so you can watch it finish, see how much succeeded, and catch what failed — without refreshing individual products. This page explains what a job records, what each status means, and what you can do to a job that needs attention. For the shared vocabulary, see Core concepts.

​
What a job tracks

Imports, enrichment runs, document ingestion, publishing, and exports all run as jobs. Each job records its type and its progress as it works through its items:
​
one of ten types
What the job is doing. Every type is filterable on the Jobs page: Enrichment, Crawl, Ingestion (document extraction), Import, Price Import, Price Publish, Catalog Publish, Oracle Sync (a scheduled inbound feed), Export, and Bulk Delete.
​
count
How many items the job set out to process.
​
count
How many items have finished so far.
​
count
How many items couldn’t be completed.
​
count
How many items finished with a warning rather than cleanly — for example, an enrichment run that found no new data to add.
​
count
How many items are paused waiting on a person. While this is above zero the job cannot finish — see Awaiting review below.
​
percentage
How far along the job is, computed from processed against total.

​
Job statuses

A job’s final status is derived from those counters, so the status tells you exactly what happened without opening the job.
completed means zero failures and zero warnings — always. A job with failed items never lands on completed. If some items succeeded and some failed, the status is partial_success (“Completed with Errors”); if nothing succeeded at all, it’s failed. So after a run with failures, partial_success is the status to look for — it is the normal outcome, not an anomaly.

​
Awaiting review

awaiting_review is the one non-terminal end state: the run did all the work it could, but some items need a human decision before the job can settle. The Jobs page shows it in purple, labelled Awaiting review; hovering explains that the job is paused on a person and nothing advances until it’s resolved. Once the reviews are cleared the job resumes its normal status ladder — nothing is lost in the meantime. Two things park a job here, and they’re resolved in different places:
  • Document ingestion. An uploaded product PDF whose extraction didn’t clear the confidence bar pauses for review. Resolve it on the document’s extraction review page — opening the job takes you there. This is the common case: the default ingestion setting parks a great many product PDFs this way.
  • Enrichment escalations. When escalation is enabled for your organization, an enrichment run that isn’t confident enough to apply a match raises it for review instead of guessing. These are resolved in the Agent Inbox.
Open the job to see which of the two is waiting; the job links you to the right screen.
Agent Inbox appears in the sidebar with a pending-review count. It is the destination for enrichment escalations only — an escalation is a match the enrichment pipeline was not confident enough to apply, raised for a person rather than guessed at. Escalations are not produced unless escalation is switched on for your organization, so for most organizations the Agent Inbox stays empty. Documents parked for extraction review are not routed here: they are resolved on the document’s own review page.
Two different statuses render on the same yellow badge: completed_with_warnings (“Warnings”) and partial_success (“Completed with Errors”). They mean very different things — the first lost no data, the second has real item failures. Read the label and the failed count, not the color.

​
Monitoring jobs

Track jobs on the Jobs page, which shows each job’s type, status, counts, and progress percentage in real time. Filter by status, by any of the ten job types, or by date. You can also read a job’s progress through the API when you’re wiring MerchantOps into your own systems.
1

Start a batch operation

Import or export a set of products, upload a document, publish a batch, or let enrichment run — each creates a job.
2

Watch progress

The job’s progress percentage climbs as its processed count rises toward total.
3

Resolve anything paused

If the job shows Awaiting review, open it and clear the review. It won’t finish on its own.
4

Review the outcome

Check the final status and the failed count. Completed with Errors means some items need a second look.
A job that finishes as Warnings did finish and lost no data — for enrichment it usually means the product already had everything, or no trustworthy source produced anything new. Review the warned items rather than treating it as an error.

​
Acting on a job

Open a job to act on it:
  • Retry Unfinished — re-queues only the items that never finished, on the same job, so you keep watching one job from start to finish instead of chasing a second one. The button shows how many items it would re-queue. If nothing is left to retry, every remaining failure is terminal (for example a product key that doesn’t resolve) and would just fail again.
  • Cancel Job — stops a job that is still pending, queued, or in progress. Jobs that have already finished can’t be cancelled.
From the Jobs list you can also select several jobs at once and Cancel the in-flight ones, Archive finished ones (they move out of the Active view — switch View to Archived to see them again), or Delete them permanently. A job must be finished or archived before it can be deleted; cancel it first if it’s still running.

Data ingestion

How products get into MerchantOps — the imports that create jobs.

How enrichment works

Enrichment runs as a background job over your products.