Skip to main content

Delete Item

Removes an item from the specified queue using the provided item ID.

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Icon - The custom icon of the node.
  • Inputs - The number of input ports of the node.
  • Outputs - The number of output ports of the node.

Input​

  • Item ID - Represents the unique identifier of the item you want to delete from the queue.

How It Works​

The Delete Item node permanently removes an item from a Robomotion Queue:

  1. Receives the Item ID of the queue item to delete
  2. Sends a delete request to the Robomotion Orchestrator API
  3. The Orchestrator removes the item from the queue permanently
  4. Returns success or error response
  5. The message passes through unchanged

Requirements​

  • Item ID must be provided (typically from Get Next Item or Wait Item output)
  • The item must exist in the queue
  • Appropriate permissions to delete from the queue

Error Handling​

Error CodeDescriptionSolution
Core.Queue.Delete.ErrOnCreateFailed to parse node configurationVerify node configuration is valid JSON
Core.Queue.Delete.OnMessageMessage parsing failedCheck input message format is valid
Core.Queue.Delete.OnMessage"Get item id error"Ensure Item ID input is provided and is a valid string
Core.Queue.Delete.OnMessageHTTP request errorCheck network connectivity to Robomotion Orchestrator
Core.Queue.Delete.OnMessageAPI returned errorVerify item exists and you have permissions to delete it
Core.Queue.Delete.OutputMarshalFailed to serialize outputCheck message structure is valid

Usage Examples​

Example 1: Delete After Successful Processing​

Remove item after it's been successfully processed:

[Get Next Item] → Output: itemId, itemData
    ↓
[Process Order Data]
    ↓
[Update Database]
    ↓
[Delete Item]
    Input Item ID: ${itemId}

Result: Item removed from queue after successful processing

Example 2: Delete Invalid Items​

Remove items that fail validation:

[Get Next Item] → Output: itemId, itemData
    ↓
[Validate Data]
    ↓ (validation failed)
[Log Error: "Invalid data format"]
    ↓
[Delete Item]
    Input Item ID: ${itemId}

Result: Invalid item removed to prevent repeated processing

Example 3: Cleanup Old Items​

Delete items based on business logic:

[Get Items] → Output: items array
    ↓
[Loop through items]
    ↓
[Check if item.createdAt > 30 days ago]
    ↓ (yes)
[Delete Item]
    Input Item ID: ${item.id}

Result: Old items cleaned up from queue

Usage Notes​

  • Deletion is permanent - deleted items cannot be recovered
  • Delete immediately after processing to keep queue clean
  • Do not delete items that may need retry - use Update Item State instead
  • Item ID typically comes from Get Next Item or Wait Item nodes
  • Failed deletions will throw an error (unless Continue On Error is enabled)
  • Deleting non-existent items will result in an error

Tips​

  • Delete items only after confirming successful processing
  • For items that might need retry, use Update Item State with "Successful" status instead
  • Log the Item ID before deletion for audit trail
  • Use Continue On Error cautiously - failed deletions might indicate issues
  • In error scenarios, consider moving items to a "failed" queue instead of deleting
  • Combine with Get Items to bulk delete old or invalid items
  • Don't delete items during processing - wait until completion
  • Consider archiving important data before deletion
  • Monitor deletion failures as they may indicate permission or connectivity issues