Skip to content

Commit d161028

Browse files
committed
Add note to README on precision of scheduled job timing
1 parent e17d9bd commit d161028

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,9 @@ If you'd like to create a job but have it run at some time in the future, you ca
136136
Job.objects.create(name='scheduled_job', run_after=timezone.now() + timedelta(minutes=10))
137137
```
138138

139-
Of course, the job will only be run if your `python manage.py worker` process is running at the time when the job is scheduled to run. Otherwise, it will run the next time you start your worker process after that time has passed.
139+
Of course, the scheduled job will only be run if your `python manage.py worker` process is running at the time when the job is scheduled to run. Otherwise, it will run the next time you start your worker process after that time has passed.
140+
141+
It's also worth noting that, by default, scheduled jobs run as part of the same queue as all other jobs, and so if a job is already being processed at the time when your scheduled job is due to run, it won't run until that job has finished. If increased precision is important, you might consider using the `queue_name` feature to run a separate worker dedicated to only running scheduled jobs.
140142

141143
## Terminology
142144

0 commit comments

Comments
 (0)