Event Sync and Live Queires are returning the object ID as undefined

Moralis General
#1

We have built our own event listener system to listen to the smart contract events via event sync service and receive such events into our backend servers with the help of the Live Query service. We are facing a serious unstable issue with this service for the past 3 hours

Context of the issue:
When the events are broadcasted to the BE servers via the Live queries service, the ObjectId for the event is sent as undefined which causes our system to fail to process the event. But when we restart our backend server/update the event info directly in the Moralis database, ATM the events are received with the ObjectId. Not sure about the behavior

Attaching the screenshots below for your reference,

moralis issue 1
moralis issue 11940×1586 372 KB

moralis issue 2
moralis issue 21634×1588 434 KB

We are using the Moralis V1 SDK in our backend server and Nest.js

#2

previously it worked without issues and this started to happen only since ~3 hours ago?

#3

Yes, it was working earlier

#4

It looks like sometimes the id is present and sometimes a _localId field from what I tested now with a live query in the browser, that local id doesn’t look like it has the same format as the id

you can try streams API, it should work better

#5

we’ll have to check more, we did an update to servers today

#6

We are not going to use the stream API atleast for now, we would be using them in near future. We have built our own event listener architecture already and will be using them until we replace it with streams API.

BTW, we need to continue with what we have implemented already, can you guys fix this issue as priority ? Since we have planned for production launch and it is got affected due to this.

#7

it may be fixed in few hours

#8

Nice to know, it would be really helpful if it is fixed ASAP. Thanks for the support

#9

it seems to be fixed now from my tests, you can try to update the server to latest version (it will take some time) or wait until it will get updated automatically to latest version

#10

you can check now on your server to see if it is fixed

#11

It seems working for us on both the Testnet versions and Mainnet versions. But wanted to make sure that these types of errors will create a long downtime for our product and It would be good to take extra care when upgrading the servers without affecting these services.

#12

I can see some 502 bad gateway errors from the Moralis.Query service when I try to retrieve some data from the Moralis MongoDB database.

Error response:

"error": "\"Received an error with invalid JSON from Parse: <html>\\r\\n<head><title>502 Bad Gateway</title></head>\\r\\n<body>\\r\\n<center><h1>502 Bad Gateway</h1></center>\\r\\n<hr><center>nginx/1.18.0 (Ubuntu)</center>\\r\\n</body>\\r\\n</html>\\r\\n\""

I suspect that this error is coming from the Moralis Parse Server, can you please check this issue as well? This issue is also only happening since yesterday

we are using the same Moralis-V1 SDK for this with our Nest.js backend server

Thanks in advance