Store Commerce hangs on Hardware Station Ext async calls

[Aeid-github]

We are running Store Commerce App v9.44.23256.14, and we have a Hardware Station Extension to connect with an automated cash drawer peripheral device.
The Hardware Station Extension makes async calls to the peripheral API and hangs around the 13th call until it times out. Please note that the peripheral API is still operational because we can still communicate with it from other apps using the same credentials and we have done multiple tests.
Only Store Commerce is hanging. also note that the same extension we have on the old retail SDK for the MPOS and it works fine with issues.
we did some changes recommended by the third party (Paypod) and now the app hangs on the 6th transaction. Reviewing the event log I can see now errors related to hardware station, could you kindly support on this
"Sending the hardware station request through the named pipe failed with exception: System.Threading.Tasks.TaskCanceledException: A task was canceled.
at Microsoft.Dynamics.Commerce.StoreCommerce.PipeCommunication.PipeClient.SendAsync(String message)
at Microsoft.Dynamics.Commerce.StoreCommerce.PipeCommunication.PipeClient.SendAsync(HardwareStationRequestMessage hardwareStationRequestMessage)
at Microsoft.Dynamics.Commerce.StoreCommerce.HardwareStation.Tasks.HardwareStationProxy.SendRequest(HardwareStationRequestMessage request). Pipe Client Connected Value: True."

another event viewer error:
"The cash drawer operation failed, retrying again at service level. Exception: System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {CCB90042-B81E-11D2-AB74-0040054C3719} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).
at System.Runtime.Remoting.RemotingServices.AllocateUninitializedObject(RuntimeType objectType)
at System.Runtime.Remoting.Activation.ActivationServices.CreateInstance(RuntimeType serverType)
at System.Runtime.Remoting.Activation.ActivationServices.IsCurrentContextOK(RuntimeType serverType, Object[] props, Boolean bNewObj)
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
at System.Activator.CreateInstanceT
at Microsoft.Dynamics.Commerce.HardwareStation.Peripherals.DevicePlugin.GetDeviceHandleTBase,TInherit
at Microsoft.Dynamics.Commerce.HardwareStation.Peripherals.OPOSDeviceManager1.AcquireDeviceHandle[TInherit](Boolean retryWithOposInitializationUponFailure) at Microsoft.Dynamics.Commerce.HardwareStation.Peripherals.OposCashDrawer.Open(String peripheralName) at Microsoft.Dynamics.Commerce.HardwareStation.Peripherals.OposCashDrawer.Execute(Request request) at Microsoft.Dynamics.Commerce.Runtime.CommerceRuntime.<ExecuteCore>d__581.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.Dynamics.Commerce.Runtime.CommerceRuntime.d__58`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
"

Once those errors show up, you cannot submit anymore transactions unless you restart the MPOS.

[Aeid-github]

Requesting update on the above issue