What is Job Priority?
A ranking that determines which jobs get executed first when resources are constrained.
Definition
Job priority is a ranking system that determines the order in which jobs are processed when multiple jobs are waiting in a queue. Higher-priority jobs are executed before lower-priority ones, regardless of when they were queued. Priority levels might be numeric (1-10) or categorical (critical, high, normal, low). Priority becomes important when system load is high and not all jobs can execute simultaneously.
Simple Analogy
Like an emergency room triage system — patients with life-threatening conditions (high priority) are seen before those with minor issues (low priority), regardless of arrival order.
Why It Matters
When your scheduling system is under load, not all jobs can run at exactly their scheduled time. Priority ensures that critical jobs (payment processing, security alerts) are never delayed by less important ones (report generation, cache warming). Proper prioritization keeps your most important automation reliable.
How to Verify
Review your job's priority setting in your scheduling system. Monitor whether high-priority jobs consistently execute with lower latency than low-priority ones. Check if any high-priority jobs are being delayed by lower-priority work.
Common Mistakes
Making everything high priority (which is the same as having no priority system at all). Not adjusting priorities as business needs change. Setting static priorities without considering the dynamic impact of job duration on queue congestion.
Best Practices
Use 3-5 priority levels maximum for clarity. Reserve the highest priority for genuinely critical jobs. Default new jobs to normal priority and promote only when justified. Review priorities quarterly to ensure they still reflect business importance.
Documentation
Read the full docs
Try it free →Frequently Asked Questions
What is Job Priority?
Job priority is a ranking system that determines the order in which jobs are processed when multiple jobs are waiting in a queue. Higher-priority jobs are executed before lower-priority ones, regardless of when they were queued. Priority levels might be numeric (1-10) or categorical (critical, high, normal, low). Priority becomes important when system load is high and not all jobs can execute simultaneously.
Why does Job Priority matter for cron jobs?
When your scheduling system is under load, not all jobs can run at exactly their scheduled time. Priority ensures that critical jobs (payment processing, security alerts) are never delayed by less important ones (report generation, cache warming). Proper prioritization keeps your most important automation reliable.
What are best practices for Job Priority?
Use 3-5 priority levels maximum for clarity. Reserve the highest priority for genuinely critical jobs. Default new jobs to normal priority and promote only when justified. Review priorities quarterly to ensure they still reflect business importance.
Related Terms
Job Queue
An ordered list of pending jobs waiting to be picked up and executed by workers.
Worker
A process or thread that picks up and executes jobs from a queue.
Execution Latency
The delay between a job's scheduled time and when it actually begins executing.
Concurrency Policy
A rule that defines behavior when a new job run is triggered while a previous run is still active.