Queue item specific data size limit

Help Orchestrator
,
1

we tried creating a queue item through the orchestrator API, but it returned the error:

{“message”:“Uploaded specific data is too large; max size is 1048576 bytes”,“errorCode”:1865,“resourceIds”:null}

Is there a way to increase this limit?

We’re using studio enterprise and orchestrator

2

@hallgrimur

The default setting is limited to 1MB for Orchestrator Performance

image
image1463×304 35 KB

I suggest raising the issue to the Technical team regarding the limitation issue as you have enterprise license

Hope this may help you

Thanks

1 Like
3

@hallgrimur

Also check below documentation for increase of the limitation

image
image1496×175 24.1 KB

Hope this may help you

Thanks

4

This only applies for on premise orchestrator.
We have orchestrator in the cloud, but we did get a response from tech support stating that we should not store such quantity of data in a queue item and rather have a link to acquire that data from something else instead.

So we are going to solve this differently

1 Like
5

I’ll not question the reasons why you would add so much data to your queue items as transactional fields.
I agree with the top response text: if you need more, store it in an external location (a txt file, excelfile, whatever) and refer to that file with a specificcontent value of just a few bytes.

All that data for each item will fill up your database, and will hinder your platforms performance over time, for something that you need only for one transaction at one time.

Our (attempt at) best practice is to keep the # of activities in a dispatcher component as low as possible, and the amount of data stored in a queue as low as possible. Often, just storing the reference to an order, ticker or document, and then runtime, access the blobs of data further required only during your process/perform phase, to be discarded directly after.

Still might not work in your setup though…

1 Like