Inventory Sync Order of Events

Owned by Kevin Vogle, created
Last updated: Jun 15, 2021
1 min read

The following chain is how the sync works. If any of the steps fail, subsequent steps will not execute. For example, if step 4.b fails, then 4.c, 4.d, 4.e, 4.f and 4.g will not execute.

If step 4.g does not execute, this will result in inventory slots not showing as available on the PDP because processed orders that are not removed take up inventory slots. Need to check function logs to see if the prior functions are working or throwing an error.

 

  1. TimerTrigger fires InventorySync function

  2. InventorySync function executes the ActivityTrigger GetInventoryPoolsToUpdate function

  3. InventorySync then executes the SyncInventoryPool Orchestration function for each result of #2 above.

  4. Each SyncInventoryPool invocation calls the following ActivityTriggers in this order:

    1. GetNopData - get UnityInventory data from Nop

    2. GetUnityData - call Unity to get current inventory counts

    3. UpdateInventory - update existing UnityInventory in Nop

    4. AddNewInventory - add new UnityInventory in Nop

    5. RemoveDeletedInventory - remove old UnityInventory records

    6. StopProcessing - set IsProcessing = 0

    7. RemoveProcessedOrders - remove UnityOrderLock records

 

 

Filter by label

There are no items with the selected labels at this time.