Using since_id and limit not starting at oldest orders?
Can it be that we miss orders when using since_id and limit together? Or has the behavior for this changed lately?
Example: lets say the lastest imported order has id 12345 and since then there are 10 new orders. If my request is: orders.json?since_id=12345&limit=5, we expected to get the oldest 5 orders directly after 12345...
I implemented this a couple of weeks ago, and I did debug on this! Because I also needed to revert the sort-order of the orders so I could import the oldest as first.
Today our client contacted us, that they missed older orders....😨
When debugging again, it seems indeed that we get the youngest 5 orders, leaving a gap for the 5 older ones. So now I wonder if I did overlook something or not....😳
Is the response for this api-request changed? Or did I miss something?
If this is the normal behavior, can you please give us an option to define the sort-order also? Else we need to make extra (unnecessary) calls to the api to determine which orders to import.
Thanks in advance,