Queue

A queue in Qrambo is a container that manages Tasks requiring review. Each queue is associated with an organization and operates within a designated environment.

While queues can contain diverse tasks, we recommend maintaining task uniformity within each queue.

Examples of queue names: refund_requests, damage_reports, fraud_detections, sales_followup, support_inquiries

Your organization may have these queues all together

Properties

name: A unique identifier for the queue (must contain only lowercase letters, numbers, underscores, hyphens, and dots)
alias: An optional display name for the queue
description: An optional description detailing the queue's function
reviewer_frontend_url: An optional URL for the reviewer interface in MyQrambo
default_assignment_strategy: Configuration for task assignment to reviewers. This can be specified during assignment.

Default Assignment Strategy

The assignment strategy determines task distribution to reviewers:

seconds_to_expire: Assignment expiration time (minimum 10 seconds)
order: “fifo” (First In, First Out) or “lifo” (Last In, First Out)
priority_order: Task priority handling
- important_first: Lower priority tasks assigned first
- important_last: Higher priority tasks assigned first
- no: Priority not considered

For additional details on assignment strategy, see the Assignment section.

QUEUE_CREATED
QUEUE_DELETED

Best Practices

Use clear, descriptive Queue names
Monitor Queue status regularly
Configure queue Notifications for Task events to be able to get results of the tasks.
Use queue level Notification instead of task level notification for Task events.
Use homogenous tasks within a queue to avoid context switch cost for your human reviewers.