You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm noticing an issue with the alpaca node client version 2.12.1 where after the trade_ws socket successfully connects it does not emit events for programmatically generated order events. It DOES emit order events if, for example, I create or cancel orders through the alpaca website. However, for orders generated programmatically such as in the node client, as well as other alpaca api clients, the trade_ws.onOrderUpdate handler does NOT emit events. This behavior seems unexpected.
If this is expected, can you please confirm ? If this is unexpected, could you advise on a setting that might cause this ? Or else a debugging strategy to isolate why this behavior would occur ?
Thanks.
The text was updated successfully, but these errors were encountered:
I'm noticing an issue with the alpaca node client version
2.12.1
where after thetrade_ws
socket successfully connects it does not emit events for programmatically generated order events. It DOES emit order events if, for example, I create or cancel orders through the alpaca website. However, for orders generated programmatically such as in the node client, as well as other alpaca api clients, thetrade_ws.onOrderUpdate
handler does NOT emit events. This behavior seems unexpected.If this is expected, can you please confirm ? If this is unexpected, could you advise on a setting that might cause this ? Or else a debugging strategy to isolate why this behavior would occur ?
Thanks.
The text was updated successfully, but these errors were encountered: