Inventory Sync Order of Events
- Kevin Vogle
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.
TimerTrigger fires InventorySync function
InventorySync function executes the ActivityTrigger GetInventoryPoolsToUpdate function
InventorySync then executes the SyncInventoryPool Orchestration function for each result of #2 above.
Each SyncInventoryPool invocation calls the following ActivityTriggers in this order:
GetNopData - get UnityInventory data from Nop
GetUnityData - call Unity to get current inventory counts
UpdateInventory - update existing UnityInventory in Nop
AddNewInventory - add new UnityInventory in Nop
RemoveDeletedInventory - remove old UnityInventory records
StopProcessing - set IsProcessing = 0
RemoveProcessedOrders - remove UnityOrderLock records
Filter by label
There are no items with the selected labels at this time.