Messing results for different queries on same account?

Hello,

We are facing strange behaviour when querying for account transactions for different periods.
The error can be reproduced this way:
First query for transactions on a given day (expected result: no transactions):
curl 'https://deep-index.moralis.io/api/v2/0x207ca4370639120f9A049aF9CAB4fCaa608F2445/erc20/transfers?chain=polygon&from_date=1655036166&to_date=1655122566' -H 'X-API-Key: <api key>'
Then, for the same account, we query for a longer period (a year):
curl 'https://deep-index.moralis.io/api/v2/0x207ca4370639120f9A049aF9CAB4fCaa608F2445/erc20/transfers?chain=polygon&from_date=1623586566&to_date=1655122566' -H 'X-API-Key: <api key>'
First execution get no results:
{"total":0,"page":0,"page_size":100,"cursor":null,"result":[]}
But when it is executed again, it returns the correct result.
The same goes if, after consuming all results, we use the first query (for a day without transactions). The first time it gets results not related to the period specified. The second time we execute the same query, it works fine.

Hi, does this still happen?

curl 'https://deep-index.moralis.io/api/v2/0x207ca4370639120f9A049aF9CAB4fCaa608F2445/erc20/transfers?chain=polygon&from_date=1623586566&to_date=1655122566' -H 'X-API-Key: <api key>'
First execution get no results:

This seems to be ok on my end (getting results the first time).

Still same error.
Being query_day = curl 'https://deep-index.moralis.io/api/v2/0x207ca4370639120f9A049aF9CAB4fCaa608F2445/erc20/transfers?chain=polygon&from_date=1655036166&to_date=1655122566' -H 'X-API-Key: <api key>'
and query_year = curl 'https://deep-index.moralis.io/api/v2/0x207ca4370639120f9A049aF9CAB4fCaa608F2445/erc20/transfers?chain=polygon&from_date=1623586566&to_date=1655122566' -H 'X-API-Key: <api key>'
Got:

  • query year: {“total”:223,“page”:0,“page_size”:100,“cursor”:"eyJhbGciOi … }
  • query day: {“total”:223,“page”:0,“page_size”:100,“cursor”:"eyJhbGciOi…}
  • query day: {“total”:0,“page”:0,“page_size”:100,“cursor”:null,“result”:[]}

I am able to reproduce this issue, thanks for reporting

it should be fixed now