Requirements Configuration name workers recycle timeout compress save_limit sync queue_limit label catch_up redis django_redis cpu_affinity Tasks Async Groups Synchronous testing Connection pooling Reference for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to

Requirements Configuration name workers recycle timeout retry compress save_limit sync queue_limit label catch_up redis django_redis disque_nodes disque_auth iron_mq sqs bulk cache cpu_affinity Brokers Redis for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to

Compatibility Configuration name workers recycle timeout retry compress save_limit sync queue_limit label catch_up redis django_redis disque_nodes disque_auth iron_mq sqs orm mongo mongo_db bulk cache cached scheduler for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to

Compatibility Configuration name workers recycle timeout retry compress save_limit sync queue_limit label catch_up redis django_redis disque_nodes disque_auth iron_mq sqs orm mongo mongo_db bulk cache cached scheduler for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to

Compatibility Configuration name workers recycle timeout retry compress save_limit sync queue_limit label catch_up redis django_redis disque_nodes disque_auth iron_mq sqs orm mongo mongo_db bulk cache cached scheduler for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to

Compatibility Configuration name workers recycle timeout retry compress save_limit sync queue_limit label catch_up redis django_redis disque_nodes disque_auth iron_mq sqs orm mongo mongo_db bulk cache cached scheduler for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to

Compatibility Configuration name workers recycle timeout retry compress save_limit sync queue_limit label catch_up redis django_redis disque_nodes disque_auth iron_mq sqs orm mongo mongo_db bulk cache cached scheduler for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to

Compatibility Configuration name workers recycle timeout retry compress save_limit sync queue_limit label catch_up redis django_redis disque_nodes disque_auth iron_mq sqs orm mongo mongo_db broker_class bulk poll for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to

Compatibility Configuration name workers recycle timeout retry compress save_limit sync queue_limit label catch_up redis django_redis disque_nodes disque_auth iron_mq sqs orm mongo mongo_db broker_class bulk poll for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to

Compatibility Configuration name workers recycle timeout retry compress save_limit sync queue_limit label catch_up redis django_redis disque_nodes disque_auth iron_mq sqs orm mongo mongo_db broker_class bulk poll for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to