Successful tasks Failed tasks Scheduled tasks Queued tasks Signals Available signals Subscribing to a signal Architecture Signed Tasks Broker Pusher Worker Monitor Sentinel Timeouts Scheduler Stop procedure signals.pre_enqueue signal is emitted before a task is enqueued. The task dictionary is given as the task argument. Before executing a task The django_q.signals.pre_execute signal is emitted before a a task is executed by a worker. This signal provides two arguments: task: the task dictionary. func: the actual function that will be executed. If the task was created with a function path, this argument

tasks Failed tasks Scheduled tasks Queued tasks Errors Signals Available signals Subscribing to a signal Architecture Signed Tasks Broker Pusher Worker Monitor Sentinel Timeouts Scheduler Stop procedure signals.pre_enqueue signal is emitted before a task is enqueued. The task dictionary is given as the task argument. Before executing a task The django_q.signals.pre_execute signal is emitted before a a task is executed by a worker. This signal provides two arguments: task: the task dictionary. func: the actual function that will be executed. If the task was created with a function path, this argument

tasks Failed tasks Scheduled tasks Queued tasks Errors Signals Available signals Subscribing to a signal Architecture Signed Tasks Broker Pusher Worker Monitor Sentinel Timeouts Scheduler Stop procedure signals.pre_enqueue signal is emitted before a task is enqueued. The task dictionary is given as the task argument. Before executing a task The django_q.signals.pre_execute signal is emitted before a a task is executed by a worker. This signal provides two arguments: task: the task dictionary. func: the actual function that will be executed. If the task was created with a function path, this argument

tasks Failed tasks Scheduled tasks Queued tasks Errors Signals Available signals Subscribing to a signal Architecture Signed Tasks Broker Pusher Worker Monitor Sentinel Timeouts Scheduler Stop procedure signals.pre_enqueue signal is emitted before a task is enqueued. The task dictionary is given as the task argument. Before executing a task The django_q.signals.pre_execute signal is emitted before a a task is executed by a worker. This signal provides two arguments: task: the task dictionary. func: the actual function that will be executed. If the task was created with a function path, this argument

signals.pre_enqueue signal is emitted before a task is enqueued. The task dictionary is given as the task argument. Before executing a task The django_q.signals.pre_execute signal is emitted before a a task is executed by a worker. This signal provides two arguments: • task: the task dictionary. • func: the actual function that will be executed. If the task was created with a function path, this argument Documentation, Release 0.9.0 1.13.2 Subscribing to a signal Connecting to a Django Q signal is done in the same manner as any other Django signal: from django.dispatch import receiver from django_q.signals

signals.pre_enqueue signal is emitted before a task is enqueued. The task dictionary is given as the task argument. Before executing a task The django_q.signals.pre_execute signal is emitted before a a task is executed by a worker. This signal provides two arguments: • task: the task dictionary. • func: the actual function that will be executed. If the task was created with a function path, this argument the callable function nonetheless. Subscribing to a signal Connecting to a Django Q signal is done in the same manner as any other Django signal: from django.dispatch import receiver from django_q.signals

signals.pre_enqueue signal is emitted before a task is enqueued. The task dictionary is given as the task argument. Before executing a task The django_q.signals.pre_execute signal is emitted before a a task is executed by a worker. This signal provides two arguments: • task: the task dictionary. • func: the actual function that will be executed. If the task was created with a function path, this argument Documentation, Release 1.3.6 1.13.2 Subscribing to a signal Connecting to a Django Q signal is done in the same manner as any other Django signal: from django.dispatch import receiver from django_q.signals

following signals during its lifecycle. Before enqueuing a task The django_q.signals.pre_enqueue signal is emitted before a task is enqueued. The task dictionary is given as the task argument. 44 Chapter Release 1.3.6 Before executing a task The django_q.signals.pre_execute signal is emitted before a task is executed by a worker. This signal provides two arguments: • task: the task dictionary. • func: the callable function nonetheless. 1.13.2 Subscribing to a signal Connecting to a Django Q signal is done in the same manner as any other Django signal: from django.dispatch import receiver from django_q.signals

will raise a TransactionManagementError. You may also encounter this behavior when an ORM-related signal handler raises an exception. The correct way to catch database errors is around an atomic block django.test.signals.setting_changed signal that lets you register callbacks to clean up and otherwise reset state when settings are changed. Django itself uses this signal to reset various data: Overridden Django calls flush to reset the database state. This empties all tables and emits the post_migrate signal, which re-creates one content type and three permissions for each model. This operation gets expensive

will raise a TransactionManagementError. You may also encounter this behavior when an ORM-related signal handler raises an exception. The correct way to catch database errors is around an atomic block serialized data from being loaded twice, setting serialized_rollback=True disables the post_migrate signal when flushing the test database. Other test conditions Regardless of the value of the DEBUG setting django.test.signals.setting_changed signal that lets you register callbacks to clean up and otherwise reset state when settings are changed. Django itself uses this signal to reset various data: Overridden