"Add to queue: Forbidden" Error after migrating to Cloud Orchestrator

Hi, we have a process that worked perfectly fine on the on-premise Orchestrator and after migrating to Cloud, the dispatcher is throwing an error when trying to add a transaction item to the queue.

After debugging, it turned out that the item is not being added if the string is too long.
For example, we have a following value of the SQL query that needs to be stored in the queue item:

“UPDATE [DataVaultProd].[dbo].[Records] SET ProcessingState = ‘ManuallyHandled_Skipped’ where IntegrationIdOut = ‘123412123Subscription1234’ and ProcessingState = ‘ProcessingFailed’ and sourceid NOT IN (select top 1 id from [DataVaultProd].[dbo].[RecordContainers] where IntegrationIdOut = ‘123412123Subscription1234’ and DataSource = ‘1234’ order by sortvalue desc, CreatedDateTime desc)”

Once it’s being added to the queue as an argument of the ItemInformation property of “Add Queue Item” activity, it throws the error: “Add to queue: Forbidden”

If we cut the string to the below length, the item will be added to the queue:
“UPDATE [DataVaultProd].[dbo].[Records] SET ProcessingState = ‘ManuallyHandled_Skipped’ where IntegrationIdOut = ‘123412123Subscription1234’ and ProcessingState = ‘ProcessingFailed’ and sourceid NOT IN (select top 1 id fro”

I think it is a bug as it worked perfectly fine on the on-premise orchestrator. Could you please recommend a solution that doesn’t involve any unnecessary string manipulation?

Hello @piotrl , Welcome to the forums!

The closest I found to your concerns about size limits is this documentation:

Your original string is surely not 1 MB and therefore something else must be the issue.

Did you try to post an ordinary string with the same length as the original string but one that contains only alphanumeric characters without the SQL symbols such as =, (, ',[,] etc?

If you are able to post that plain string, it means the format of the string is in question when posting to Automation cloud.

thanks