@KarlOffenberger The order argument is still not listed in the official Order API page. Do you have an update on whether or not this will be officially supported (or deprecated) in the near future?
Adding some context on my specific case:
We're building a pipeline to ingest Shopify Orders via the API. Every hour, we look at the max(updated_at) in our shopify database and use it as our updated_at_min argument to call the Orders API. Between each call (pagination), we append the data to our database and remove duplicates before going to the next page. When running the script, we do not store orders from previous pages in memory to use as little memory as possible and avoid out-of-memory issues.
By default, the API gives orders ordered by updated_at desc. If our ingestion script breaks in the middle of its run, there will be a missing entries (with updated_at < new max(updated_at)) that we will ignore in the next job run.
Of course, we could avoid this situation by keeping in memory the orders from all the pages on our machine before sending them to the database, but that is not memory efficient. I'm quite sure I'm not the only one building such ingestion pipelines from the Orders API and the `order` argument is very useful here to have an optimised ingestion.
