Can Orchestrator handle all queue data, or is a seperate SQL server needed?

Trying to develop a best-practice, we are discussing the need for an external SQL server, to hold queue data, used by multiple robots accessing the same Orchestrator Queue.

Is there ever a viable need for a seperate SQL Server, or does the Orchestrator meet all needs of a queue accessed by several robots doing the same process? I dont know if I explained this in a way that makes sense, I hope i did…

Hi @Mikkel_Nielsen

The core idea behind queues is for them to be accessible by many robots that can then process data in parallel. I believe queue items only support basic data types for now, but supporting more is on the roadmap.