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
We don’t have an exact timeline yet, they are already deprecated in the sense that new customers can not create servers any more.
Yeah, we are using a legacy plan and we have access to this. I hope the deprecation might not happen before the mid of next month. Please send us a notification/updates regarding this
you should be fine if you are able to finish the migration in a month
The old server are going to close within a month?
that was not decided at this moment, we will keep them for at least one more month
Keep in mind @Venkatesh_OP @lolicon131452 that you do the migration as soon as possible. We have no ETA for this, but it will be in your best interest to migrate as soon as possible as you will decrease the risk of losing access to your server permanently. We have reminded this many times so we hope that you take action to migrate promptly.
There are no information/personalized email updates about this deprecation for the legacy users (We know it is already deprecated for new users) so far, so it would be good to have this information communicated before taking down the servers
Yes, no worries @Venkatesh_OP. It will be given announcement when the time is due and of course enough amount of time for migration. As for now, it has not been the case for paid legacy user. My suggestion is just not to do it at the very last minute as it posed a risk to your app in the future.
This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.