Configuring Task Queues in Bitrix24 Flows
Tasks pile up faster than the team can handle them. Without queues, everything gets mixed up: an urgent client task gets lost among routine requests, and a critical bug waits while an employee finishes a low-priority task. Queues in Bitrix24 flows organize incoming work: tasks line up by priority, are processed in order, backlog is controlled.
How a Queue Works
When a task enters a flow and cannot be immediately assigned (all executors are busy, task limit reached), it enters a queue. The queue is a buffer between task creators and executors.
Tasks in the queue are sorted and processed by rules:
- FIFO (First In, First Out)—whoever came first is served first. Tasks are processed strictly in arrival order. Simple option, suitable for uniform requests.
- By priority—high-priority tasks are processed first, regardless of arrival time. A critical bug arriving 5 minutes ago bypasses a normal task waiting 2 hours.
- Combined—priority first, within one priority—FIFO.
Priorities in the Queue
Bitrix24 supports task priorities: Critical, High, Normal, Low. In queue context, priorities determine processing order.
Configuration:
| Priority | Queue Order | Maximum Wait Time |
|---|---|---|
| Critical | First | 15 minutes |
| High | After critical | 1 hour |
| Normal | After high | 4 hours |
| Low | Last | 8 hours |
If a "Critical" priority task waits longer than 15 minutes—escalation triggers: notify flow manager, automatically expand task limits for executors.
Backlog Management
Backlog—tasks in the queue not yet assigned. Backlog control is critical:
- Monitor queue size. If backlog grows—the team can't handle the incoming flow. Signal for the manager: need to add staff or reconsider priorities.
- Queue limit. Maximum tasks in queue. When limit is reached, new tasks aren't accepted (task creator sees a warning) or auto-redirect to another flow.
- Auto-cleanup. Tasks in queue longer than specified time without processing are marked overdue and escalated.
Queue Visualization
The flow manager sees the queue as a sorted list by priority and arrival time. Available information:
- Number of tasks in queue.
- Average wait time.
- Distribution by priorities.
- Tasks approaching SLA violation.
What We Configure
- Choose queue model: FIFO, priority-based, combined
- Task priorities and max wait time for each
- Escalation rules when wait time exceeded
- Backlog limit and overflow actions
- Monitoring: queue dashboard for flow manager
- Team training: working with priorities, tracking queue