Unique handling in orders sync

What is the purpose of this article?

The purpose of this article is to provide the resolution on how we can avoid bugs occuring on workspace (status mismatch bugs, export bugs).

This article also mentions the steps taken to resolve the previous BUGS in complete detail and any unique handling that was done in case of status mismatch.
In this article, we will mainly discuss this bug https://auperator.atlassian.net/browse/BUGS-15040

Unique handling done in order sync to avoid the status mismatch

1. If intransit/out_for_delivery/failed_delivery is received after delivered event in shipment_status_logs table in DB

   1. What was the issue - Due to Race condition, Workspace shows intransit/out for delivery status but the order is delivered in customer portal.

   2. Resolution - We query and fetch the latest shipment_status_log.status from DB on the basis of external_updated_at. If external_updated_at is null or 0, then we pickup created_at at its place. i.e., we are sorting the status on the basis of shipment_status_logs.external_updated_at from DB.

2. Unique handling done failed_to_rts/failed_to_handover

   1. If failed_to_rts/failed_to_handover is received after cancelled, then we are setting currentOrderStatus,orderstatus = cancelled in algolia

   2. if failed_to_rts is received after packed then we are checking if algolia object contains packed timeStamp (not null), then we are setting currentOrderStatus,orderstatus = null

   3. if failed_to_rts/failed_to_handover is received after an rto event then we are checking if algolia object contains packed timeStamp (not null), then we are setting currentOrderStatus,orderstatus = null

   4. if failed_to_handover is received after intransit/out_for_delivery/failed_delivery then we are checking if algolia object contains onTheWayTimestamp (not null), then we are setting currentOrderStatus,orderstatus = null

3. Handling done for contact_customer_care status in shipment_sttatus_logs/return_sghipment-status_logs table in DB

   1. contact_customer_care status will get ignored in Algolia sync as well as in export

4. Unique handling to be done when any forward shipment status is received after delivered status in DB and the external_updated_at date of that forward shipment status is greater than delivered status’s external_updated at.