Sync doesnt sync in real time anymore

Technical Issue Reporting
#1

Hi. I was happily using “Sync and Watch Contract Events” to watch a contract in rinkeby. It was working flawlessly, almost real time!
Then I made some changes to the contract and I deployed and updated everything to make it work.
Everything is the same but now it takes like 4 minutes to sync in each browser ( i mean to show the create subscription event in each user’s browser).

Any ideas?
PS. my server is 4awmj3mczjmy

#2

Did you recreate (not update) the sync for your new contract? Try restarting your server.

#3

The event arrives faster in the database? You can look at creation time

#4

yep. tried both… still doesnt sync fast.

#5

I looked at creation time in terminal.
The tx is listened by the server in real time, but it is written to the db three to four minutes later.

photo_2022-07-30 13.00.40
photo_2022-07-30 13.00.40487×602 65.4 KB

#6

it is written twice in db, once with confirmed false and once with confirmed true

#8

OK! so, if I understand correctly, before, the synced tx was written into DB with a “confirmed” false flag, thats why It seems to be done in real time.
Now, the tx is synced and written into DB after the tx is confirmed. Thats why It takes like two or three minutes.

How can I change this new behavior?. I need the tx to be written with “confirmed” false flag…

#9

it may depend on the code that you use now, how do you get that event?

1 Like
#10

Thanks cryptokid for the responses.
But this is going a little deeper :

  • I discovered that when I make a transaction through REMIX directly , the server show a Log meaning the table in the db was written (with “confirmation” FALSE flag. ). After some minutes it flags the confirmation as true. This works flawlesly and real time.
    photo_2022-07-30 19.51.22
    photo_2022-07-30 19.51.22657×1278 231 KB
  • IF if make the transaction through the UI, from client browsers, then the server listens to the tx, but it does not write it in the table’s DB, until its confirmed a couple minutes later…
    photo_2022-07-30 13.00.40
    photo_2022-07-30 13.00.40487×602 65.4 KB

I dont get what may be going on exactly…

#11

What you mean with doing a transaction through the UI?

#12

For UI, I mean: through a web browser running a this webpage im developing which calls metamask…

#13

This behaviour is consistent? Which chain is this on? You can post both transaction hashes.

The transaction is made with the same wallet address?

#14

if the transaction is on chain, it shouldn’t matter how it was done

1 Like
#15

However the problem remains the same.
When I make the tx interacting with the contract through REMIX, the moralis’server DB is written with “cofirmed” false flag.
When I do the same thing from my UI (a DAPP), moralis’s server DB is only written after confirmation is true, which means three to four minutes after the tx is done.

Just to clarify, in both cases I use metamask as wallet to make the tx, just that in the first example I use REMIX, and in the second I use my DAPP.

I tested several times now. I still dont know what the heck is going on with this weird behaviour :man_shrugging: … Im still stucked.

#16

Are you using the latest Moralis SDK for your app (+ react-moralis)? And try updating your server if you haven’t.

#17

Nope, no react, im using just vainilla.
Im using the last moralis server version.

#18

Can you share your serverUrl. Have you tested on another testnet?

I get the normal behaviour in vanilla JS (executeFunction) for a Goerli contract with my server (initially with confirmed: False).

1 Like
#19

it should be no difference between those two cases

1 Like