Thanks. I appreciate the help. I feel a bit silly I never thought to check that. FWIW, I would suggest that better behavior would have been an error from the API.  

FYI, I used the patch I mentioned to submit a request. (previous example may have had a typo)the x-request-id for this job isf8397cfb-218c-4562-998d-79c02cf66377 Submitted just before: Thu, 21 May 2020 18:34:20 UTC +00:00 Job returned 96 objects. Exp...

FYI, I have submitted a pull request to try and make getting the request-id possible for graphql queries. If you have someone at Shopify who works on your clients, I'd love to get some feedback  on it. https://github.com/github/graphql-client/pull/24...

No problem. This is a test store: gratzi-test-store.myshopify.comgid://shopify/BulkOperation/7140573243submitted Thu, 21 May 2020 between 13:40 and 13:43 UTC. The bulk operation returned all objects in the store. It should have returned 0.

Hi Hassain, Can you give me some more direction here? the item you referenced seemed to apply to the REST api vs graphql. I've traded the query from ShopifyAPI gem here: https://github.com/Shopify/shopify_api/blob/master/lib/shopify_api/graphql/http_...

adding the quotes had no effect How do I enable the logging to get a request id? I'm using the ruby client.

I've kept working at this, and been trying non-bulk operations, e.g. just regular queries I cannot get querying by created_at working in either. I have verified that querying by updated_at is working for regular queries (I have not verified bulk) So,...

I am attempting to fetch data with createdAt or updatedAt properties in a certain window. Exactly like the example on the tutorial page for products: https://shopify.dev/tutorials/perform-bulk-operations-with-admin-api mutation { bulkOperationRunQu...