Slow Track

Slow Track is a low-priority message processing channel that you can use to handle non-urgent, long-running tasks without affecting the performance of higher-priority channels.

Slow Track provides these benefits:

Segregate low-priority work from urgent processing
Prevent non-urgent tasks from consuming resources needed for critical operations
Maintain overall system performance by managing workload distribution
Handle tasks that can wait without affecting business operations

Slow Track is used for these items:

Low priority messages: Documents that don't require immediate processing
Long-running processes: Tasks that naturally take extended time
Batch operations: Large volumes processed gradually
Not time-sensitive: Documents without deadlines

Slow Track is not used for these items:

Urgent business transactions
Real-time processing requirements
Time-sensitive integrations
Critical system alerts

This table shows the comparison between Slow Track and Fast Track behavior:


Aspect	Slow Track	Regular Track	Fast Track
Channel	Low priority, background processing	Medium priority, standard processing	High priority, urgent processing
Priority Level	Lowest	Medium	Highest
Resource allocation	Minimal during peak hours	Standard allocation	Maximum resources
Processing window	Continuous background	Business hours priority	Immediate processing
Queue	Can accumulate backlog	Steady processing	Minimal queue time
Priority processing during simultaneous operation	Runs in background, processing messages only when both Fast Track and Regular Track have available capacity May experience delays during peak periods but continues processing through anti-starvation mechanism	Processes concurrently with Fast Track but yields resources when Fast Track has pending messages Maintains steady processing when Fast Track is idle	Receives highest priority and processes continuously while messages are available Gets immediate access to processing resources

The resource competition is in this order: Fast Track > Regular Track > Slow Track. All channels can process simultaneously, but higher priority channels take precedence when resources are constrained.