GWMS Manual

English

中文

English

中文

Appearance

View Agent Warehouse Logs in GWMS ​

Updated: 2026-08-06

1. Scenario ​

The agent warehouse logs page shows the request and response records exchanged between GWMS and the agent warehouse. It answers "what was sent, what came back" — use it after Sync Tasks has already flagged an issue, to pin down exactly which request failed and what result it returned.

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

  • You've already seen a failed task on Sync Tasks and want to see the raw request/response;
  • You want to confirm whether the order number, warehouse, SKU, or channel GWMS sent to the agent warehouse was correct;
  • You want to confirm whether an inbound serial number was actually pushed to the agent warehouse, or whether the agent warehouse brought inbound/outbound serial numbers back to GWMS;
  • You want to confirm whether the agent warehouse returned a failure, an empty result, or has already processed successfully;
  • You want to quickly locate a specific API call by order number or error keyword.

Recommended troubleshooting order:

  1. Check Sync Tasks first to confirm whether the task is waiting, successful, or in manual handling.
  2. If the task summary already points to a configuration, master data, or local action issue, fix that first.
  3. If you still need to confirm the exact API call details, then go to the logs page for the request and response body.

2. View Logs ​

2.1 Open the Logs Page ​

Menu path: GWMS > Agent Warehouse > Logs

The page supports searching by these conditions:

  • 【System Name】: select the agent warehouse system
  • 【Business】: select the operation type, e.g. push, cancel, query
  • 【Business Keyword】: enter an order number or SKU
  • 【Request URL】: enter the API endpoint
  • 【Request Body】: search request content
  • 【Response Body】: search response content

Common search methods:

  1. Search by order number: enter the business order number or third-party order number in 【Business Keyword】.
  2. Search by error: enter keywords like "failed", "error", "exception" in 【Response Body】.
  3. Search by API: enter part of the endpoint in 【Request URL】 to narrow the range.

2.2 View Log Details ​

Click the 【View】 button to see:

  • Request URL: the API endpoint called
  • Request Body: the full content sent
  • Response Body: the full content returned by the agent warehouse

The system automatically formats JSON content for easier reading.

2.3 What This Page Is Good For Answering ​

This page is best suited for confirming:

  • Whether GWMS actually sent the request out;
  • Whether the warehouse, order number, SKU, channel, and quantity sent were correct;
  • Whether the serial number content sent was correct, and what the agent warehouse returned for serial number entry, query, or update;
  • Whether the agent warehouse's status response actually included inbound or outbound serial numbers, and whether the local side had a chance to write them back into GWMS;
  • Whether the agent warehouse has clearly returned success, failure, or an empty result;
  • Whether the result changed across multiple automatic retries of the same task.

This page does not directly tell you "did the business ultimately close out". If the agent warehouse already returned success but a subsequent local action failed, you still need to go back to Sync Tasks to check the task status and execution summary.

2.4 Checking Logs for Serial Number Issues ​

If you're troubleshooting a serial number issue, check in this order:

Scenario 1: Suspect GWMS didn't push the inbound serial number to the agent warehouse

  1. Search logs by the business order number first.
  2. Focus on the serial number entry, serial number query, and serial number update request types.
  3. Confirm whether the warehouse, SKU, and serial number content in the request are correct.

Scenario 2: Suspect the agent warehouse didn't write the inbound serial number back to GWMS

  1. Search the inbound status query logs by the inbound order number first.
  2. Confirm whether the agent warehouse's response actually included serial number content.
  3. If the response has no serial numbers at all, the issue is on the agent warehouse response side.
  4. If the response has serial numbers but GWMS didn't save them, keep troubleshooting from the mapping and main flow side.

Scenario 3: Suspect the agent warehouse didn't write the outbound serial number back to GWMS

  1. Search the outbound status query logs by the outbound order number first.
  2. Confirm whether the product node in the agent warehouse's response carries a serial number list.
  3. If the response has serial numbers but the local side didn't sync them, go back to Sync Tasks to confirm whether the main flow has actually advanced to completion.

3. Common Questions ​

Q: What's the difference between Logs and Sync Tasks?

A:

  • Sync Tasks: shows what step this business operation is currently at — successful, waiting for retry, or needs manual handling.
  • Logs: shows exactly what this specific step sent, and what the agent warehouse responded with.

Recommendation: check Sync Tasks first. If you need to pin down the exact cause of an error, then check Logs.

Q: Can't find any log records?

A:

  • Confirm whether the business operation actually triggered a agent warehouse request
  • Try searching by order number using 【Business Keyword】 first
  • Go to the Sync Tasks page to confirm whether a task was actually created

Q: The response body shows no obvious error, but the business still failed?

A: This usually means the agent warehouse API already returned success, but a subsequent local action didn't complete. Go back to Sync Tasks and check the execution summary and error message.

Q: There are too many logs — how do I narrow it down?

A: Combine 【System Name】 + 【Business Keyword】, or 【Request URL】 + 【Business】 first. If there are still too many, narrow the range further by created time.

Q: After reviewing the logs, what should I do next?

A:

  • If you've identified a configuration issue, go back to Agent Warehouse System to fix it.
  • If you've already fixed it and want to run it again right away, go back to Sync Tasks and click 【Sync Now】.
  • If it's an HPK-specific issue, such as inventory interpretation or current support scope, keep reading HPK Guide.

Q: Why don't serial number issues stand out on the Sync Tasks page?

A: The current serial number flow does not generate a separate serial number task. Whether it's the local side pushing an inbound serial number to the agent warehouse, or the agent warehouse bringing serial numbers back to GWMS in an inbound/outbound result, you ultimately need to rely on the log records, and cross-reference them with the inbound or outbound task status.