Broker was harvesting a page with URL https://imin.strmln.uk/api/open-active/orders-rpde?afterTimestamp=1729596298655551&afterId=6c81ae8e-4272-48c9-821d-56211754bba9, and it contained a next URL which pointed to https://imin.strmln.uk/api/open-active/orders-rpde?afterTimestamp=1729596298650499&afterId=6c81ae8e-4272-48c9-821d-56211754bba9. This latter URL has a lower timestamp than the former URL. This should be impossible as items should be ordered by timestamp in ascending order.
RPDE ordering not working as expected could lead to all sorts of issues, like data being missed by the client, the client being sent into a loop and so never getting new data, getting data in the wrong order, etc.
It also stops Test Suite from passing as soon as it's spotted
(This error was reported by Broker Microservice)
Broker was harvesting a page with URL
https://imin.strmln.uk/api/open-active/orders-rpde?afterTimestamp=1729596298655551&afterId=6c81ae8e-4272-48c9-821d-56211754bba9, and it contained anextURL which pointed tohttps://imin.strmln.uk/api/open-active/orders-rpde?afterTimestamp=1729596298650499&afterId=6c81ae8e-4272-48c9-821d-56211754bba9. This latter URL has a lower timestamp than the former URL. This should be impossible as items should be ordered by timestamp in ascending order.RPDE ordering not working as expected could lead to all sorts of issues, like data being missed by the client, the client being sent into a loop and so never getting new data, getting data in the wrong order, etc.
It also stops Test Suite from passing as soon as it's spotted