Priority

Priority in Qrambo determines the importance and processing order of tasks within queues. It helps ensure that critical tasks are handled appropriately.

Task priority can be set during task creation or modified during operation.

Use Cases

Operational vs Training

Priority can be used to differentiate between operational and training tasks. For example, in a “patient fall detection” system, real-time fall detections would have higher priority than offline AI training data. This ensures that reviewers process time-sensitive operational tasks before handling non-urgent training data.

With this approach, you can utilize your reviewers’ time more efficiently.

Service Levels

Similarly, priorities can be used to manage service levels, such as prioritizing tasks based on user subscription tiers. So of our users prioritize free-tier users’ tasks first because their growth is more important than retention.

Urgency Changes During Operation

If you get a complaint from a user, you can increase the priority of the task to ensure it is handled quickly.

Range

Following the German prioritization system, lower numbers indicate higher priority.

• Minimum: 5 (highest priority)
• Maximum: 995 (lowest priority)
• Default: 500

Usage

1. Task Creation:

{
  "input_data": { ... },
  "priority": 100
}

2. Task Update:

Task priorities can be modified using expressions operations:

• Set absolute priority: N
• Increase current priority: +N
• Decrease current priority: -N
• Complex expression: (N*2)+12

3. In Assignment Strategy:

{
   // other assignment data
  "priority": 'important_first' | 'important_last' | 'no'
}

Get more information about Assignment Strategy.

Best Practices

1. Avoid priority inflation
2. Regular priority review
3. Balance workload across priorities
4. Consider business impact
5. Monitor priority distribution