odata/QueueItems PUT - Reference is not updating

Help Orchestrator
1

I am trying to use Orchestrator HTTP Request to update the Reference of a Queue Item. I am calling odata/Queueitems(key) and passing this as the payload:

image
image327×257 2.82 KB

I am getting HTTP status 200 success, and the queue item shows in Orchestrator that it was updated:

image
image664×164 13.7 KB

However, the Reference is not updated:

image
image633×115 5.64 KB

The success is happening when I do it with Swagger (although the reference isn’t updated). However when I try the same API call with Orchestrator HTTP Request I get status 404.

2

Hey @postwick ,

We cannot edit/change the reference of the queue item once created either manually or using API.
It can only be done when creating or cloning the queue item.

Thanks

3

This is all so ridiculous, we’ve been asking for these capabilities for years.

I need to do the following:

  • Get Transaction
  • Get Queue Items (New)
    • For Each to get just the ones where two SpecificContent values match
  • Mark all Queue Items as In Progress

Because we can’t directly edit the Status from New to In Progress, I thought I’d update the Reference to the Id as the original Transaction, then use Get Transaction and specify that Reference to mark it as In Progress.

But now I can’t even edit the Reference to be able to use Get Transaction.

This complete inability to manage Queue Items with activities or the API is maddening.

4

Hi @postwick,

If the requirement is batch processing, you can design it like this:

  • Instead of adding individual items, you can group related data (e.g., in a DataTable/JSON) and push it as one queue item
  • After Get Transaction Item, iterate through the DataTable and process each record

Alternatively,

  • Use the Reference field while adding queue items to group related transactions
  • Then use Get Transaction Item to process them sequentially

Thanks!

5

I can’t do either of those things. We need to be able to manage Queue Items properly, we’ve been requesting this on the forums for YEARS.

6

Hi @postwick,

If we manage to mark all related transactions as In Progress, what should be the next step? Should we process only the current transaction and then mark the remaining related transactions as completed, or is there a recommended approach to handle them individually?

Thanks!

7

The next step is finishing the process and then marking them Success/Fail.

The point is when I Get Transaction I also need to get other Queue Items to process as a group.

8

Hi @postwick,

As in your case adding Reference is not possible while pushing data into the queue, you can use an alternative approach:

  • Use a secondary queue
  • Design a bot to:
  • Get transaction items from the primary queue
  • Add them into the secondary queue** with the required Reference/structure
  • Once done for all, → Process the transaction using secondary queue.

Thanks!

9

Hey Paul,

I’ve tested and confirm your findings that the queue item indeed doesn’t update the reference with the PUT request, so the documentation in the swagger page must be wrong.

I’d question your overall architecture to need this approach, but thats a fairly moot point at this stage.

The API to set a queue item from New to In Progress is not documented in Swagger if I recall correctly, but you can do it from Studio.
Without unpacking the underlying code for the activity, you can intercept the API call when the normal activity runs to see what it is, then replicate that with the Orchestrator HTTP request, doing so I believe you can set it using the key items ID or key, not the reference.