Skip to content

Track Agent Warehouse Sync Tasks in GWMS

Updated: 2026-08-06

1. Scenario

The Sync Tasks page tracks the execution results of agent warehouse business. After triggering an inbound push, outbound push, cancel confirmation, inventory sync, or status write-back, warehouse staff can use this page to check task status, execution summary, HTTP logs, and inventory snapshots — and manually trigger a one-time 【Sync Now】 when needed.

This guide is for warehouse operations, implementation, and troubleshooting staff. Common use cases include:

  • Checking whether an inbound or outbound order has completed agent warehouse sync;
  • Deciding whether a task is still waiting, currently running, already successful, or needs manual handling;
  • Opening task details to view request logs and error messages;
  • Viewing the agent warehouse inventory snapshot captured by an inventory sync task;
  • Manually running 【Sync Now】 on an unfinished task.

This page is meant to be the first stop in the operations workflow:

  • After pushing a business operation, come here first to check the result.
  • Use this page to decide whether to keep waiting, click 【Sync Now】, or fix configuration/master data first.
  • If you need to see the specific request and response, go to Logs next.

2. Steps

Prerequisites

  1. Your account can access GWMS > Agent Warehouse > Sync Tasks.
  2. The target business operation has already triggered a agent warehouse interaction, and a task has been created in the system.
  3. To run 【Sync Now】, confirm the task is not already in 【Success】 or 【Cancelled】 status.

2.1 Open the Sync Tasks Page

Menu path: GWMS > Agent Warehouse > Sync Tasks

  1. After logging in to GWMS, open the 【Agent Warehouse】 module in the left sidebar.
  2. Click 【Sync Tasks】.
  3. The page has three sections:
    • Filter bar (top): search conditions
    • Task overview (middle): quick statistics and navigation
    • Task list (bottom): task detail table

Available filter conditions

  • 【Status】: select the current task status
  • 【Business Type】: select inbound, outbound, or other business types
  • 【Task Type】: select the task category, including:
    • Query task: poll the agent warehouse again for this business operation's latest status
    • Create task: confirm whether the inbound/outbound order has been accepted and is being processed by the agent warehouse
    • Cancel task: confirm whether the cancel action has completed at the agent warehouse
    • Inventory sync task: pull an inventory snapshot from the agent warehouse and correct GWMS-managed inventory
  • 【Warehouse】: select a specific warehouse
  • 【Created Time】: select a date range

Task type reference

The system currently supports 4 task types:

Task TypeMeaningUse Case
Query taskStatus re-checkAutomatic or manual re-check of this business operation's latest status at the agent warehouse
Create taskCreate confirmationConfirm the inbound/outbound order has been accepted and is being processed by the agent warehouse
Cancel taskCancel confirmationConfirm whether the cancel action has completed at the agent warehouse
Inventory sync taskInventory correctionPull an inventory snapshot from the agent warehouse and sync it into GWMS-managed inventory

Additional notes:

  • Serial-number-related capability does not currently generate a 5th task type here.
  • In the existing code, serial number scenarios break down into at least 4 cases: post-creation push for inbound, incremental sync for inbound serial number changes, agent warehouse inbound result write-back, and agent warehouse outbound result write-back.
  • If you need to troubleshoot why a serial number didn't push out or didn't come back, check Logs first for the corresponding request and response, then come back here and cross-reference the inbound/outbound task status to see whether the main flow has closed out.

What to focus on here when checking serial numbers:

  • Check whether the inbound or outbound order's main flow is already successful, still waiting, or in manual handling.
  • Check whether 【Execution Summary】 mentions a main-flow failure, a failed local action, or that it's still waiting for the next query.
  • Don't read "task successful" as automatically meaning "serial numbers have definitely been fully written back" — serial number write-back and the main flow's result aren't strictly equivalent.

2.2 Use the Task Overview to Quickly Spot Exceptions

The task overview area is designed for quickly filtering tasks by risk level.

Overview card structure

  • Top: 【Task Overview】 label and a help icon
  • Right side: 【Expand】/【Collapse】 toggle button
  • Primary metrics area: shows key statistics
  • Filter hint bar: shows the active filter condition after a metric is selected
  • Expanded area: shows more secondary metrics and action reminders

Primary metrics

Each metric card shows:

  • Metric name
  • Count
  • Color indicator: red (needs handling), yellow (attention), blue (informational)
  • Clickable filter: clicking auto-filters the list

Common metrics include:

  • Backlog task count: tasks currently still waiting and not yet complete
  • Running task count: tasks currently being executed
  • Tasks requiring manual handling: tasks where the automatic flow has stopped and needs human intervention

Recommended usage

Suggested workflow:

  1. Start with the backlog, running, and manual-handling metrics to quickly spot exceptions.
  2. When a metric looks abnormal, click the corresponding card.
  3. The system auto-filters to the matching set of tasks.
  4. After handling, click 【Clear Filter】 to return to the full task list.

If you're mainly troubleshooting an inventory sync issue, filter 【Task Type】 to "Inventory Sync Task" first, then check the overview.

Expanded area content

When expanded, this shows:

  • Secondary metrics: additional statistical dimensions
  • Action reminders: risk alerts worth paying attention to

2.3 View the Task List

The task list has 6 main columns:

【Order No.】 column

Two lines:

  • Line 1: business order number (clickable for details, copyable)
  • Line 2: third-party order number (if available, copyable)

【Type】 column

Two lines:

  • Line 1: task type (create task, cancel task, query task, inventory sync task)
  • Line 2: business type (inbound, outbound, etc.)

【Status】 column

Shows the current task status:

  • Waiting (yellow)
  • Running (blue)
  • Success (green)
  • Manual handling (red)
  • Cancelled (grey)

How to read these statuses:

  • Waiting: this task hasn't finished. The common case is the system has already scheduled the next automatic query or retry — it doesn't necessarily mean the agent warehouse is processing it right now.
  • Running: the system is currently executing this task — avoid repeatedly clicking 【Sync Now】.
  • Success: this task has fully closed out.
  • Manual handling: the automatic flow has stopped — check configuration, master data, business status, or local action preconditions first.
  • Cancelled: this task has been closed and will not run again.

【Route Info】 column

Shows the configuration associated with this task:

  • GWMS warehouse code
  • Agent warehouse code
  • Agent warehouse system code

【Execution Summary】 column

Shows a result description or error message, used to quickly identify the cause of success or failure.

【Time】 column

Shows three timestamps:

  • Created time
  • Last executed time
  • Next execution time (if the task is still waiting)

【Actions】 column

  • 【Sync Now】 button: only shown for unfinished tasks
  • Tasks that are already successful or cancelled no longer show this button

2.4 View Task Details

  1. Click the business order number in the task list.
  2. The task details dialog opens.
  3. The default 【Task Details】 tab shows:
    • Task ID
    • Task type
    • Task status
    • Business type
    • Business order number / third-party order number
    • Agent warehouse system information
    • Warehouse code / agent warehouse code
    • Request ID
    • Last executed time / next execution time / created time
    • Execution result
    • Error message

If this task has associated request records, the details dialog also shows a 【Request Logs】 tab. Inventory sync tasks additionally show a 【Agent Warehouse Inventory】 tab.

2.5 View Request Logs

  1. In the task details dialog, switch to 【Request Logs】.
  2. The list shows the API records associated with this task.
  3. Expand a row to see request content on the left and response content on the right.

Use this to confirm:

  • Which API was called
  • Whether the order number, warehouse code, and SKU in the request are correct
  • Whether the agent warehouse returned success, failure, or an empty result

2.6 View the Inventory Sync Task Snapshot

When the task type is "Inventory Sync Task", the details dialog shows an extra 【Agent Warehouse Inventory】 tab.

This tab mainly shows the agent warehouse inventory snapshot saved when this inventory sync task ran, with these fields:

FieldDescription
Agent warehouse SKUSKU code in the agent warehouse system
GSKUGlobal SKU in GWMS
Local SKUCustomer-side SKU code
Available inventoryAvailable quantity returned by the agent warehouse
Locked inventoryLocked quantity returned by the agent warehouse
Total inventoryAvailable inventory + Locked inventory
Inventory typeQualified goods / Defective goods
Agent warehouse inbound orderInbound order number recorded by the agent warehouse
Local inbound orderGWMS inbound order number
Inbound timeInbound time recorded by the agent warehouse
Snapshot timeTime this task captured the snapshot
Agent warehouse codeAgent warehouse's warehouse code
GWMS warehouse codeGWMS warehouse code

How to read the snapshot data:

Important notes:

  • This tab shows the inventory snapshot captured at the time the task ran — it is not a live re-query of the agent warehouse.
  • Use it to trace "why this particular sync run produced this result".
  • To see the current latest inventory, trigger a new inventory sync task.

Inventory quantity calculation rules:

  • Total inventory = Available inventory + Locked inventory
  • Don't treat "available inventory" as GWMS's total directly
  • Always factor in locked inventory when calculating the total
  • Comparing only available inventory can easily lead to a false mismatch conclusion

Inventory detail split rules:

The agent warehouse splits inventory by inbound batch when returning it. During GWMS sync, the following are mainly used to match a batch to the correct record:

  • Warehouse
  • SKU
  • Inventory type (qualified goods / defective goods)
  • Inbound order number
  • Inbound time

Note:

  • GWMS only corrects the proxy-warehouse-managed dedicated locations (virtual shelving location, defective product location) — it does not modify other general locations.

2.7 Manually Run Sync Now

  1. On the row of an unfinished task, click the 【Sync Now】 button.
  2. A confirmation dialog appears: "Confirm execute this task immediately?"
  3. After confirming, the system shows "Execution request submitted".
  4. Refresh the list or wait a moment, then check the task status and execution summary.

If execution fails, the page shows the failure reason directly.

How Sync Now works:

After clicking 【Sync Now】, the system prioritizes putting this task back into the execution queue immediately, instead of waiting until its originally scheduled next execution time.

When to use it:

Recommended scenarios for using 【Sync Now】:

  • The agent warehouse has already finished processing, but the local task is still waiting for the next query
  • You just fixed a mapping, system configuration, or master data issue and want to run it again right away
  • You need to verify whether a fix for a specific issue has taken effect

Not recommended to click repeatedly in these scenarios:

  • The task is already successful or already cancelled
  • The task is still being processed
  • The root cause of the error hasn't been resolved yet — for example, system configuration, warehouse mapping, or SKU data is still wrong

What to watch after execution:

Clicking only submits the execution request. The task still needs to go through actual execution, query, and write-back. Keep in mind:

  • Check whether 【Last Executed Time】 has updated first
  • Then use 【Execution Summary】 to judge the result
  • If the status is still "waiting", the system has decided it still needs further automatic query or retry
  • If the status changes to "manual handling", the automatic flow alone can no longer complete it

3. Additional Notes

3.1 Automatic Query Intervals

The system schedules the next query or retry differently depending on task type:

Task TypeAutomatic IntervalNotes
Create task30 minutesCreate confirmation tasks re-check by default every 30 minutes
Cancel task10 min → 20 min → 1 hour → 4 hoursCancel confirmation task interval increases with retry count
Inventory sync task12 hoursRetries on a 12-hour cadence after an execution error
Query task24 hoursStatus re-check tasks re-check again after 24 hours by default

Notes:

  • Create task (inbound/outbound): fixed 30-minute re-check interval
  • Cancel task: 10 minutes the 1st time, 20 minutes the 2nd time, 1 hour the 3rd time, 4 hours from the 4th time onward
  • If you don't want to wait, click 【Sync Now】 to trigger manually

3.2 Common Task Statuses

StatusMeaningDescription
WaitingNot yet finishedThe task is waiting for the next automatic query or retry, or has just been put back into the execution queue
RunningCurrently executingThe task is executing — don't repeatedly click 【Sync Now】 during this round
SuccessCompleteThe task has fully closed out
Manual handlingNeeds interventionThe automatic flow has stopped; common causes include a agent warehouse failure, an unrecognizable status, a local action precondition not being met, an auto-cancel being blocked, or consecutive failures exceeding budget
CancelledClosedThe task has been cancelled and will not run again

3.3 When Sync Now Makes Sense

Recommended scenarios for using 【Sync Now】:

  • The agent warehouse has already finished processing, but the local task is still waiting for the next query
  • You just fixed a mapping, system configuration, or master data issue and want to run it again right away
  • You need to verify whether a fix for a specific issue has taken effect

Not recommended to click repeatedly in these scenarios:

  • The task is already successful or already cancelled
  • The task is still being processed
  • The root cause of the error hasn't been resolved yet — for example, system configuration, warehouse mapping, or SKU data is still wrong

3.4 Inventory Sync Tasks vs. Business Sync Tasks

Inventory sync tasks are only responsible for inventory correction — they don't correspond to one specific business order. Their focus is:

  • Pulling the agent warehouse snapshot
  • Comparing it against local inventory
  • Recording the agent warehouse inventory detail used in this run

Note:

  • Inventory sync doesn't wait indefinitely for every other business task in the same warehouse to finish first;
  • The system only tries to clear part of the pending business tasks for that warehouse, then continues with inventory correction;
  • So an inventory sync succeeding does not mean every business task in that warehouse has already fully closed out.

Business sync tasks, on the other hand, focus on whether a specific inbound order, outbound order, or cancel action has completed.

4. Common Questions

Q1: Why is there no 【Sync Now】 button in the list?

A1: This task is usually already in a terminal state, such as 【Success】 or 【Cancelled】. The page only offers 【Sync Now】 for unfinished tasks.

Q2: I clicked 【Sync Now】 — why didn't the status change to success right away?

A2: Clicking only submits the execution request. The task still needs to go through actual execution, query, and write-back. Check whether 【Last Executed Time】 has updated first, then use 【Execution Summary】 to judge the result.

Q3: Why can't I see the 【Agent Warehouse Inventory】 tab in an inventory sync task's details?

A3: Only inventory sync tasks show this tab. Confirm you're actually looking at an inventory sync task.

Q4: The task status has been stuck at "waiting" — where should I look first?

A4: Check 【Execution Summary】 and 【Error Message】 first. If it points to an API issue, go to Logs to see the raw request and response. If it points to a warehouse, channel, SKU, customer data, or system configuration issue, go back to Agent Warehouse System and check the mapping and master data.

Q5: Why does the quantity in the inventory snapshot differ from what I see on the agent warehouse page right now?

A5: The inventory data in task details is the snapshot saved when that task ran — it does not update live as the agent warehouse's inventory changes afterward. It's meant to trace "what inventory did this task see at the time" — it's not a real-time inventory dashboard.