Hey @Venkatesh_OP,
Thanks for reaching out to us
Unfortunately, we’ll not look at any untrusted third-party link as it is a risk on our side. Can we know since when does the event stop getting added to your database?
Hey @Venkatesh_OP,
Thanks for reaching out to us
Unfortunately, we’ll not look at any untrusted third-party link as it is a risk on our side. Can we know since when does the event stop getting added to your database?
It was working good and the last event added on 09-02-2023. The events are not being added from today Morning in my time.
Hello, can you also paste the server url?
does it work as expected now? I restarted coreservices on that server, it looks like it got stuck at a connection. You can also restart coreservices programmatically if needed
Yeah, it is working right now
Can we know why the connection got stuck ? Wanted to make sure that this never happens on production env
we have to investigate more, I don’t know exactly now, it could have been a DNS issue or something else
can you paste the stream id that didn’t work as expected?
can you paste the stream id that didn’t work as expected?
Stream ID: 4d8e2665-57cf-4bfb-85e3-ec1987b2808d
we have to investigate more, I don’t know exactly now, it could have been a DNS issue or something else
Please prioritize this issue, it seems very critical for us
for that stream config, can you make another transaction on chain that emits that event?
the config for that stream looks ok to me
I have tried again but the webhook has not triggered
can you try again one more time? I updated your stream config to remove the spaces from topic0
It works now, I can get the events broadcasted with my webhooks
I restarted coreservices on that server, it looks like it got stuck at a connection
Please don’t close this ticket until this issue is resolved/identified.
Any updates on this issue ?
We didn’t find out more, we are deprecating now the use of old managed Moralis Servers, are you planning to move to using stream API?
I am facing same issue. Please help
Whats the timeline for this deprecation? Yes, we are in the process of migration
you can restart coreservices programmatically by following this forum post:
most of the times restarting coreservices is enough to fix possible issues