We are subscribing to mosaic data and confirmed transactions through an NIS web socket on the testnet. We are using the nem-sdk. We’ve been seeing inconsistent behavior where we would successfully receive confirmation messages for a particular wallet address, but not for another. I’ve also seen this behavior using stompjs, wherein I would only receive messages for 1 address but not for another. I’m not sure why this is happening. In our current scenario, we successfully receive mosaic data change (nem.com.websockets.subscribe.account.mosaics.owned) but not the confirmed transaction (nem.com.websockets.subscribe.account.transactions.confirmed) – but this same scenario works fine for another address. Any input would be appreciated.
Did you check other nodes? Still same scenerio that for specific address it doesn’t work?