# Cloud Orchestrator API QueueItems Date Filter Error

**URL:** <https://forum.uipath.com/t/cloud-orchestrator-api-queueitems-date-filter-error/709267>\
**Category:** Orchestrator\
**Tags:** postman, filter, api, odata, question, orchestrator\
**Created:** [December 28, 2023, 4:51pm UTC](https://forum.uipath.com/t/cloud-orchestrator-api-queueitems-date-filter-error/709267 "2023-12-28T16:51:28Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![c-jbring](https://sea2.discourse-cdn.com/uipath/user_avatar/forum.uipath.com/c-jbring/32/267528_2.png) [@c-jbring](https://forum.uipath.com/u/c-jbring)\
**Post date:** [December 28, 2023, 4:51pm UTC](https://forum.uipath.com/t/cloud-orchestrator-api-queueitems-date-filter-error/709267/1 "2023-12-28T16:51:29Z")

</div>

Hello All,  
We are migrating from on-premise Orchestrator to cloud Orchestrator and discovering that the API functionality differs between the two deployments. In on-prem, we are able to use the OData filter to only find certain QueueItems created or processed during specified dates. However, those same filters on the StartProcessing property do not work in the cloud API.

Below, I’m showing two screenshots from Postman: one that shows we do have 7 queueitems in the returned data when not including the StartProcessing filter, and one screenshot that shows the error “Invalid OData query options.” The only difference is the addition of the StartProcessing filter.

How do we resolve this issue? I tried using $skip and $top, but those only make sense if the OData $orderby works reliably - and it doesn’t.

Is this date filter on QueueItems a known issue with Cloud API, and if so when can we expect a resolution? How do we get around it in the meanwhile?

Thanks for any assistance,  
John

 ![Screenshot 2023-12-28 094152](https://global.discourse-cdn.com/uipath/original/4X/e/1/a/e1a8c118f7101cd5a74772c5ae1f05e9cfbb2efb.jpeg)  
 ![Screenshot 2023-12-28 094851](https://global.discourse-cdn.com/uipath/original/4X/4/f/6/4f6567cbe9865aecd637f20b540b0264f3ff7939.jpeg)

FYI, here are results coming back from the on-premise call:

 ![Screenshot 2023-12-28 105835](https://global.discourse-cdn.com/uipath/original/4X/6/f/3/6f3fc0de6c641d2eb21c25e4ebec7567c44f6d79.jpeg)

---

<div class="post-metadata">

**Author:** ![marian.platonov](https://sea2.discourse-cdn.com/uipath/user_avatar/forum.uipath.com/marian.platonov/32/260263_2.png) [@marian.platonov](https://forum.uipath.com/u/marian.platonov)\
**Post date:** [December 28, 2023, 8:00pm UTC](https://forum.uipath.com/t/cloud-orchestrator-api-queueitems-date-filter-error/709267/2 "2023-12-28T20:00:23Z")

</div>

Check this thread [Orchestrator API - Queue item filter for StartProcessing and EndProcessing - #2 by marian.platonov](https://forum.uipath.com/t/orchestrator-api-queue-item-filter-for-startprocessing-and-endprocessing/467833/2)

---

<div class="post-metadata">

**Author:** ![c-jbring](https://sea2.discourse-cdn.com/uipath/user_avatar/forum.uipath.com/c-jbring/32/267528_2.png) [@c-jbring](https://forum.uipath.com/u/c-jbring)\
**Post date:** [December 28, 2023, 8:30pm UTC](https://forum.uipath.com/t/cloud-orchestrator-api-queueitems-date-filter-error/709267/3 "2023-12-28T20:30:54Z")

</div>

I did see this post when researching the error and I added the filter as you showed. I see the same error (see screenshot).

 ![Screenshot 2023-12-28 142848](https://global.discourse-cdn.com/uipath/original/4X/2/c/a/2ca88592d19b29408681877ac9c682401a4330c9.jpeg)

---

<div class="post-metadata">

**Author:** ![marian.platonov](https://sea2.discourse-cdn.com/uipath/user_avatar/forum.uipath.com/marian.platonov/32/260263_2.png) [@marian.platonov](https://forum.uipath.com/u/marian.platonov)\
**Post date:** [December 28, 2023, 9:02pm UTC](https://forum.uipath.com/t/cloud-orchestrator-api-queueitems-date-filter-error/709267/4 "2023-12-28T21:02:19Z")

</div>

I used the below GET request, and I didn’t receive any errors:

```auto
https://cloud.uipath.com/YOUR_ORG_NAME/YOUR_TENANT_NAME/odata/QueueItems?$filter=((QueueDefinitionId eq 471724 and Status eq 'Successful' and (StartProcessing eq 2023-11-01 and EndProcessing eq 2023-11-01)))&$top=1000&$expand=Robot,ReviewerUser&$orderby=Id%20desc

```

 ![image](https://global.discourse-cdn.com/uipath/original/4X/7/3/0/730fe3b2e387d1c3669f06a293ab14a7f65a2d82.png)

---

<div class="post-metadata">

**Author:** ![c-jbring](https://sea2.discourse-cdn.com/uipath/user_avatar/forum.uipath.com/c-jbring/32/267528_2.png) [@c-jbring](https://forum.uipath.com/u/c-jbring)\
**Post date:** [December 28, 2023, 9:32pm UTC](https://forum.uipath.com/t/cloud-orchestrator-api-queueitems-date-filter-error/709267/5 "2023-12-28T21:32:42Z")

</div>

I copied your url (after “odata/QueueItems?”, of course) and plugged it in on my side and it did not work. Is there a security setting on the platform I’m missing or something?

 ![Screenshot 2023-12-28 151739](https://global.discourse-cdn.com/uipath/original/4X/6/a/7/6a7f14cb33fd712d4a3eb271815df2b98d232deb.jpeg)

---

<div class="post-metadata">

**Author:** ![Lockie\_v](https://sea2.discourse-cdn.com/uipath/user_avatar/forum.uipath.com/lockie_v/32/496784_2.png) [@Lockie\_v](https://forum.uipath.com/u/Lockie_v)\
**Post date:** [September 6, 2024, 5:53am UTC](https://forum.uipath.com/t/cloud-orchestrator-api-queueitems-date-filter-error/709267/6 "2024-09-06T05:53:46Z")

</div>

Hey there, I am experiencing the same issue, have you been able to find a solution?

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/uipath/user_avatar/forum.uipath.com/system/32/182466_2.png) [@system](https://forum.uipath.com/u/system)\
**Post date:** [January 17, 2025, 5:03pm UTC](https://forum.uipath.com/t/cloud-orchestrator-api-queueitems-date-filter-error/709267/7 "2025-01-17T17:03:36Z")

</div>

Closed on January 17, 2025, 5:03pm UTC

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
