-
Notifications
You must be signed in to change notification settings - Fork 739
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meaning of the Fulfillment-inbound-api-v2024-03-20 ListInbounPlans LastUpdateAt #4290
Comments
If I need to synchronize these data, can I incrementally obtain inboundPlan, shipments, boxes and other information through the last update time?If not, is there any other way to obtain this data incrementally? |
Hi, |
@puppsupr Okay, thanks, I probably already know the answer to the first question. Is the second question feasible? |
Now there is another problem: I found that the InboundPlan's LastUpdateAt does not effectively represent the most recent update time of the shipment
Request header:
Why does this happen? @puppsupr |
@liuguoxiang9965 The update should be due to some related change in the inbound plan. Please open a support case following the guidance here so we can further look into the reason for update. Thanks |
Fulfillment-inbound-api-v2024-03-20 Whether the last updated time field (lastUpdatedAt) returned in each shipment plan in the API listInboundPlans list interface can represent:
After the shipment, boxes, goods and other related information under the shipment plan changes, the last update time field will also change. Please elaborate on the behavior involved in causing the change in the last update time field, such as: change in the status of the shipment;Can anyone help?
The text was updated successfully, but these errors were encountered: