[SOLVED] Incorrect event topic with struct arrays

Creating a Sync with the following abi:

[{ "anonymous": false, "inputs": [ { "indexed": false, "internalType": "uint256", "name": "auctionId", "type": "uint256" }, { "components": [ { "internalType": "uint256", "name": "bidIndex", "type": "uint256" }, { "internalType": "uint128", "name": "baseAmount", "type": "uint128" }, { "internalType": "bytes32", "name": "salt", "type": "bytes32" } ], "indexed": false, "internalType": "struct RevealedBid[]", "name": "winningRevealedBids", "type": "tuple[]" }, { "indexed": false, "internalType": "uint256", "name": "filledBase", "type": "uint256" }, { "indexed": false, "internalType": "uint256", "name": "filledQuote", "type": "uint256" } ], "name": "AuctionFinalized", "type": "event" }]

results in a topic of
“AuctionFinalized(uint256,(uint256, uint128, bytes32),uint256,uint256)”
which differs from the actual topic
“AuctionFinalized(uint256,(uint256,uint128,bytes32)[],uint256,uint256)” with hash

Here is a testnet event with topic[0] “8a789…” https://goerli.etherscan.io/tx/0xd91227c4de8e0f202c86a9f39eda7d681863db804a205ee4d4ccd3bbc3792b62#eventlog

Moralis does not sync these events into the database I assume because of the incorrect topic generated

you can use the hash version of the topic directly in these complex cases
you can do that now when you add an event sync from code
if you see a number of events associated with your event sync in event sync status, then the topic is not the issue and there has to be a different issue

I created a custom event sync with the correct topic and it filled out the table thank you!
Also made a custom event sync using the same values but the incorrect topic, and as expected didn’t find any event matches