# Manage background work in WMS
URL: https://support.starshipit.com/articles/14700000000066-manage-background-work-in-wms
Canonical: https://support.starshipit.com/articles/14700000000066-manage-background-work-in-wms
Markdown: https://support.starshipit.com/articles/14700000000066-manage-background-work-in-wms.md
Updated: 2026-10-20

> For the complete documentation index, see [llms.txt](https://support.starshipit.com/llms.txt).

> Check queued work, understand errors and partial results, and choose the supported recovery action in Starshipit WMS.

Use Background Work to check long-running imports, stocktake processing and queued updates, then choose the right next step when work needs attention.

## Before you begin

You need account-wide process-log viewing access (`process-logs.view`) to open Background Work. Users restricted to selected clients cannot access this overview. Ask your WMS administrator to check your [roles and client access](/articles/14700000000036-set-up-wms-users-roles-and-client-access) if the page is missing.

Recovery actions also require the permission for the affected workflow. Viewing a failed item does not grant permission to approve stocktakes, change inventory or manage integrations.

## Find the affected work

1. Go to **System > Background Work**.
2. Choose the view that matches your task:
   * **Active work** shows running, waiting and automatically retrying work.
   * **Needs attention** shows approvals, errors and reviews that need action.
   * **Recent activity** shows work with activity in the last 24 hours.
   * **History** lets you find older work.
3. Filter by **Work type**, **Status** or **Specific event**. Use **Execution source > Tracked jobs** for an overall import or processing run, or **Queue** for individual queued updates and writebacks.
4. Match the displayed SKU, reference or other record details to the affected workflow. Check the status, progress, warning or error counts, and activity time.
5. Select **Refresh** to check again. The page also updates every 30 seconds.

A tracked job and its queued work can appear separately. Compare their references and outcomes before treating them as separate failures. If nothing appears, clear the filters and check **History** before starting the work again.

## Understand the status

| Status | What to do |
| --- | --- |
| **Waiting** or **Running** | Allow the work to progress. Use the activity time and progress to check for changes. |
| **Automatic retry** | WMS has another attempt available. Check the scheduled retry time where shown and wait before repeating the originating action. |
| **Approval needed** | An authorised user must review the stocktake before inventory changes can apply. |
| **Completed** | Verify the resulting records or stock in the relevant dashboard. |
| **Completed with issues** | Work finished with warnings or errors. Check the results and any changed records before repeating any part of it. |
| **Review needed**, **Failed**, **Retries exhausted** or **Retry needed** | Read the error and use the workflow-specific recovery below. The status alone does not mean a manual retry is available. |
| **Cancelled** | Check what completed before cancellation. Cancellation does not generally reverse work already applied. |

Use **System > Process Logs** for the detailed audit trail. For stock changes, compare the affected inventory and [stock movements](/articles/14700000000020-adjust-stock-and-investigate-stock-movements) as well as the background status.

## Choose the supported recovery action

### Stocktakes awaiting approval or processing

Select **Review stocktake** when it appears, or open **Inventory > Stocktakes**. Users with `stocktake.approve` can review the quantities and approve or decline the submission. Follow [Run stocktakes and cycle counts](/articles/14700000000015-run-stocktakes-and-cycle-counts#approve-or-decline-a-stocktake).

The stocktake progress notification does not offer a cancellation or retry button. If processing fails or completes with issues, inspect the recorded adjustments before submitting another count. Escalate an uncertain result rather than applying the same corrections again.

### Cin7 Core stock updates and writebacks

For eligible **Cin7 Core → WMS stock update** items, Background Work offers **Retry** after a failed reconciliation, review outcome or exhausted retries. This requires account-wide settings and product management permissions. Resolve the reported cause first; the Cin7 Core integration must be enabled with **Stock/AvailableStockLevelChanged** selected before the retry can queue.

Where **Resolve in Inventory** appears, open the affected product and compare its stock in both systems. A directional inventory sync requires account-wide inventory adjustment permission and can replace the destination system's quantities. Follow the [Cin7 Core reconciliation procedure](/articles/14700000000035-set-up-cin7-core-with-starshipit-wms#reconcile-an-inventory-difference) before confirming it.

This retry is not available for every Core import or outbound writeback. If a receipt, adjustment or shipment outcome is uncertain, check Cin7 Core and the process logs before repeating the WMS action. Repeating opening stock is a separate operation that can replace existing WMS stock; follow the integration guide rather than using it as a general error-recovery step.

### CSV imports and location actions

Check the completion notification and the affected dashboard for created, updated, skipped and failed records. Location and container import errors offer **More info** while that notification is available. Other imports may show a summary and a link to their records.

Product, location and purchase-order CSV imports can retain changes made before an error or cancellation. Location bulk actions also retain completed changes. Correct the affected rows or records and check what already exists before starting another operation.

Container CSV imports are different: a failed or cancelled import creates no containers. Correct the reported errors before uploading the file again. See [Import and export WMS data by CSV](/articles/14700000000041-import-and-export-wms-data-by-csv) for each file's rules.

For transfer CSV imports, use **View results** on the completion notification. To reopen an earlier result, go to Transfers, choose the file and date under **Import results**, then select **View import results**. **Retry incomplete** resumes eligible unfinished work using its saved progress; created transfers stay unchanged and transfers needing manual review are excluded. Follow [Import warehouse transfers from CSV](/articles/14700000000065-import-warehouse-transfers-from-csv) before retrying or reconciling an uncertain source order.

### Demand reviews and product syncs

Open **Generate from Demand** on the Replenishment dashboard to recover a demand review. A failed or cancelled review cannot create replenishments; start a new review. If creating jobs from a completed review has an unconfirmed result, use **Retry creation** for the same saved batch. Follow [Replenish pick faces](/articles/14700000000016-replenish-pick-faces#review-demand-before-creating-work) before changing the review or creating more work.

For a product sync, use the notification's **View products** link and check the affected products and error summary. Background Work does not offer a general retry for these tracked runs. Review the integration's guidance and any completed changes before starting another sync.

## Cancel work where supported

Use the active progress notification's cancellation control when you need to stop supported work. Closing a dialog or minimising the notification does not cancel the operation.

| Work | Cancellation control |
| --- | --- |
| Product, location, container, purchase-order or transfer CSV import | **Cancel import** |
| Location bulk action | **Cancel remaining locations**, with location management permission |
| Replenishment demand review | **Cancel review**, with account-wide replenishment access |
| Product sync that offers cancellation | **Cancel sync**; syncing products to Starshipit requires product management permission |

Transfer import cancellation requires account-wide purchase-order management permission. Container import cancellation requires inventory movement permission. The Starshipit product import, Cin7 Core product/opening-stock imports and stocktake notifications do not offer cancellation.

Wait for **Cancelling...** to change to a final result before starting replacement work. A running operation may finish its current step first. Review the final counts and records: cancellation is not an undo action, and the result may be completed if the operation finished first.

## Verify recovery or contact support

After a recovery action, refresh Background Work and check its final status. Verify the affected products, locations, stocktake adjustments or transfers. For integration changes, confirm the result in the connected system too; a queued retry or completed preparation step does not confirm the external change succeeded.

If work remains unchanged, the recovery action is unavailable, or an external outcome is uncertain, contact [Starshipit support](/ticket). Include the WMS account, work name, status, last activity time, affected references or SKUs, error text and the actions already attempted. Keep the original CSV file where relevant, and do not include passwords or API keys.