Skip to main content

Get Items

Retrieves items from a specified Queue in Orchestrator

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

if ContinueOnError property is true, no error is caught when the project is executed even if Catch node is used.

Input​

  • Progress - The progress status of the item(s) to be retrieved.
  • Priority - The priority level of the item(s) to be retrieved.
  • Status - The status of the item(s) to be retrieved.

Output​

  • Items - The retrieved items from the Queue.

Options​

  • Queue Name - The name of the queue to retrieve items from.
  • AES Key / RSA Key Pair - The encryption key for the Queue items.
info

The Queue Name option is mandatory for the node to function properly. If not provided, the node will result in an error.

How It Works​

The Get Items node retrieves multiple items from a queue based on filter criteria:

  1. Accepts filter parameters (Progress, Priority, Status)
  2. Retrieves encryption credentials from the vault
  3. Queries the Robomotion Orchestrator API with filters
  4. Receives encrypted items matching the criteria
  5. Decrypts each item using AES or RSA decryption
  6. Outputs an array of decrypted items with metadata
  7. Does NOT start transactions or modify item states

Requirements​

  • Queue Name must be specified
  • Valid encryption key (AES or RSA key pair) in vault matching the one used when adding items
  • Appropriate permissions to access the queue

Error Handling​

Error CodeDescriptionSolution
Core.Queue.GetAll.ErrOnCreateFailed to parse node configurationVerify node configuration is valid JSON
Core.Queue.GetAll.OnMessageMessage parsing failedCheck input message format is valid
Core.Queue.GetAll.ErrCredentialsInvalid or missing credentialsVerify encryption key exists in vault
Core.Queue.GetAll.OnMessage"Get queue name error"Ensure Queue Name is provided
Core.Queue.GetAll.OnMessage"Hex decode error"Data corruption - verify encryption keys match
Core.Queue.GetAll.OnMessage"AES key decode error"AES key format is invalid
Core.Queue.GetAll.OnMessage"Unsupported vault item type"Use AES Key or RSA Key Pair
Core.Queue.GetAll.OnMessageHTTP request errorCheck network connectivity
Core.Queue.GetAll.OutputMarshalFailed to serialize outputCheck message structure

Usage Examples​

Example 1: Get All Pending Items​

Retrieve all items waiting to be processed:

Queue Name: "OrderProcessing"
Progress: "new"
Priority: (all)
Status: (all)
AES Key: From vault

Output Items: [
  {id: "item1", data: {...}, tryCount: 0, maxTryCount: 3, createdAt: "...", updatedAt: "..."},
  {id: "item2", data: {...}, tryCount: 0, maxTryCount: 3, createdAt: "...", updatedAt: "..."}
]

Example 2: Get Failed High-Priority Items​

Find failed items that need attention:

Queue Name: "InvoiceProcessing"
Progress: (any)
Priority: 3 (High)
Status: 3 (Failed)

Output: Array of high-priority failed items for manual review

Example 3: Monitoring Queue Status​

Check items currently being processed:

Queue Name: "DataImport"
Progress: "inProgress"
Priority: (all)
Status: (all)

Output: List of items currently being processed by robots

Usage Notes​

  • When Continue On Error is enabled, errors are not caught even if Catch node is present
  • This node does NOT start transactions or lock items
  • Returns all items matching the filters - could be large result set
  • Items include metadata: ID, TryCount, MaxTryCount, CreatedAt, UpdatedAt
  • Data is automatically decrypted before output
  • Does not modify queue item states
  • Use for monitoring, reporting, or bulk operations
  • Not suitable for processing workflows - use Get Next Item instead

Tips​

  • Use specific filters to avoid retrieving too many items
  • For processing workflows, use Get Next Item or Wait Item instead
  • Combine with Loop nodes to process retrieved items
  • Use for queue monitoring dashboards and reports
  • Filter by Status to find Failed items needing attention
  • Check Progress "inProgress" to see what robots are currently working on
  • This node is read-only - it doesn't change item states
  • Cache credentials to avoid repeated vault lookups
  • Use for bulk cleanup operations combined with Delete Item
  • Monitor item counts to detect queue backlogs