[SOLVED] Sync event function does not update anymore

Moralis General
#1

Hi Team,
I am encountering an issue that my created event syn does not do its job anymore.
When I create a new transaction and it does not sync.
The detail relative info FYI below:

transaction hash: 0x34b80718e5fb6d5c79ca6687bf228dfc7c3351da20cd093cc0c5e02299b05d96
my server URL: https://li8crrzx4alq.grandmoralis.com:2053/server
The sync topic: ERC20Bought(address,address,address,uint,unit)
table name: SwapHistory
server type: bsctestnet

This sync event was created on 1/6. At that time I tried several transactions and it worked fine.
But Just now, I signed two transactions and it does not work.
When I look into the database, I found that in EvenSync table, it shows yesterday was the last sync_start as below:

Screen Shot 2022-01-14 at 13.18.04
Screen Shot 2022-01-14 at 13.18.041160×292 27.4 KB

Now, no matter how I do transaction and it does not sync.
As you can see the contract event on bscscan: https://testnet.bscscan.com/address/0xf5555a991bce039229f8bbb1779164eb1034355b#events
There are 6 ERC20Bought events history (2 from today, 4 from 7 days ago). But in the SwapHisotry table created by syncevent in moralis server, it only shows 4 which is from 7 days ago.
Screen Shot 2022-01-14 at 14.00.03
Screen Shot 2022-01-14 at 14.00.032232×1218 496 KB

Let me also share the eventsync setting FYI:
Screen Shot 2022-01-14 at 13.30.30
Screen Shot 2022-01-14 at 13.30.301456×1388 227 KB

Might I know how can I work it around?
Many thanks

#2

there was a problem yesterday-today, can you try again now or in 4-5 hours?

1 Like
#3

Thanks for the reply. I just realized the missing transactions have been back.

1 Like
#4

I am encountering the same issue again for another syncEvent. Might I know if it is also the issue from server, or my mis-setting?

Detail info below:
my server URL: https://li8crrzx4alq.grandmoralis.com:2053/server
The sync topic: tokenTransferred(address, uint, uint , address, address)
table name: SendBepTx
server type: bsctestnet

The sync setting:

Screen Shot 2022-01-15 at 17.26.52
Screen Shot 2022-01-15 at 17.26.52764×1406 96.9 KB

The event on bscscan(testnet):
transaction: https://testnet.bscscan.com/tx/0x29ef74f8b7fd0502a530ec0088e0b9e5b84e897c912cfca75ada22acbf33eabd

Screen Shot 2022-01-15 at 17.27.49
Screen Shot 2022-01-15 at 17.27.492874×1444 679 KB

The SendTx table (not syncing):

Screen Shot 2022-01-15 at 17.30.55
Screen Shot 2022-01-15 at 17.30.552878×1610 383 KB

Many thanks!
Eric

#5

this is not a valid topic, the topic doesn’t have to use spaces, you can search other posts on forum on how to validate the topic

#6

I appreciate your prompt reply.
After removing the space, it is still not working. please see detail below:

Screen Shot 2022-01-15 at 17.45.07
Screen Shot 2022-01-15 at 17.45.072880×1596 414 KB

Screen Shot 2022-01-15 at 17.46.48
Screen Shot 2022-01-15 at 17.46.48788×1408 120 KB

#8

that is not a valid data type, you could use directly the hash of the topic, it may be faster, instead of uint it should be uint256

#9

I tried uint256 like below, but still no luck.

Screen Shot 2022-01-15 at 18.04.00
Screen Shot 2022-01-15 at 18.04.00776×1408 124 KB

Screen Shot 2022-01-15 at 18.01.55
Screen Shot 2022-01-15 at 18.01.552876×1610 385 KB

#10

it may also take few minutes after you do it right, you can validate if you have the right topic using

you can validate if you have the right topic with a syntax like this:

web3 = await Moralis.enableWeb3()
web3.utils.sha3('LockAdded(uint256,address,address,uint256,uint256)')

and then check the resulting hash to be equal to topic0 of that event, or use directly that topic 0 in the interface for topic

#11

Yes, I did try (Copied the topic from moralis sync setting panel and hash it to compare with bscscan topic0) and found it is exactly the same. please see below. But it is still not syncing

Screen Shot 2022-01-15 at 18.28.53
Screen Shot 2022-01-15 at 18.28.531658×90 22.4 KB

Screen Shot 2022-01-15 at 18.29.16
Screen Shot 2022-01-15 at 18.29.161610×204 87.3 KB

Screen Shot 2022-01-15 at 18.29.50
Screen Shot 2022-01-15 at 18.29.501596×130 51.8 KB

#12

ok, this means that is no longer a problem related to the topic

can you try to restart your server now?

#13

It is correct to restart by the “update and restart” button below:

Screen Shot 2022-01-15 at 18.35.48
Screen Shot 2022-01-15 at 18.35.482264×710 116 KB

#14

After doing “Update and Restart” it is still not syncing, you could have a look at the screenshot below:

Screen Shot 2022-01-15 at 18.40.15
Screen Shot 2022-01-15 at 18.40.152880×1262 344 KB
Screen Shot 2022-01-15 at 18.42.00
Screen Shot 2022-01-15 at 18.42.002212×654 99.3 KB

#15

And I found it very weird is that when I look into the “EventSync” table and I found that it shows the last_synced_block is exactly the block of that transaction.
But In the table of SendBepTx --> it still remain 0 raw.
You can have a look at the screenshot below:

Screen Shot 2022-01-15 at 18.52.25
Screen Shot 2022-01-15 at 18.52.252880×992 373 KB

The setting is historical data sync “ON”:
Screen Shot 2022-01-15 at 18.58.31
Screen Shot 2022-01-15 at 18.58.31920×1578 144 KB

#16

ok, now is the problem with field names that start with _, you have to rename all those field name in the abi to not start with _: https://docs.moralis.io/moralis-server/automatic-transaction-sync/smart-contract-events#name-field-limits

#18

Thanks for your pointing out that, really helpful. The very last question is that does it mean that I will also need to modify the smart contract accordingly since the event arguments of the smart contract are all start with “_”.

#19

you don’t need to modify the smart contract, only the abi that you paste on sync event you have to modify it

1 Like
#20

Thanks so much sir, Let me have a try.

#21

Hello Sir, After trying, it is working now. I appreciate your great support

1 Like