TasksLink to this heading

The Task framework provides the contract and plumbing for background work, not the engine that runs it. The Tasks API defines how work is described, queued, and tracked, but leaves actual execution to external infrastructure.

Task definitionLink to this heading

The task decoratorLink to this heading

task(*, priority=0, queue_name='default', backend='default', takes_context=False)Link to this definition

The @task decorator defines a Task instance. This has the following optional arguments:

  • priority: Sets the priority of the Task. Defaults to 0.

  • queue_name: Sets the queue_name of the Task. Defaults to "default".

  • backend: Sets the backend of the Task. Defaults to "default".

  • takes_context: Controls whether the Task function accepts a TaskContext. Defaults to False. See Task context for details.

If the defined Task is not valid according to the backend, InvalidTask is raised.

See defining tasks for usage examples.

TaskLink to this heading

class TaskLink to this definition

Represents a Task to be run in the background. Tasks should be defined using the task() decorator.

Attributes of Task cannot be modified. See modifying Tasks for details.

priorityLink to this definition

The priority of the Task. Priorities must be between -100 and 100, where larger numbers are higher priority, and will be run sooner.

The backend must have supports_priority set to True to use this feature.

backendLink to this definition

The alias of the backend the Task should be enqueued to. This must match a backend defined in BACKEND.

queue_nameLink to this definition

The name of the queue the Task will be enqueued on to. Defaults to "default". This must match a queue defined in QUEUES, unless QUEUES is set to [].

run_afterLink to this definition

The earliest time the Task will be executed. This can be a timedelta, which is used relative to the current time, a timezone-aware datetime, or None if not constrained. Defaults to None.

The backend must have supports_defer set to True to use this feature. Otherwise, InvalidTask is raised.

nameLink to this definition

The name of the function decorated with task(). This name is not necessarily unique.

using(*, priority=None, backend=None, queue_name=None, run_after=None)Link to this definition

Creates a new Task with modified defaults. The existing Task is left unchanged.

using allows modifying the following attributes:

See modifying Tasks for usage examples.

enqueue(*args, **kwargs)Link to this definition

Enqueues the Task to the Task backend for later execution.

Arguments are passed to the Task’s function after a round-trip through a json.dumps()/json.loads() cycle. Hence, all arguments must be JSON-serializable and preserve their type after the round-trip.

If the Task is not valid according to the backend, InvalidTask is raised.

See enqueueing Tasks for usage examples.

aenqueue(*args, **kwargs)Link to this definition

The async variant of enqueue.

get_result(result_id)Link to this definition

Retrieves a result by its id.

If the result does not exist, TaskResultDoesNotExist is raised. If the result is not the same type as the current Task, TaskResultMismatch is raised. If the backend does not support get_result(), NotImplementedError is raised.

aget_result(*args, **kwargs)Link to this definition

The async variant of get_result.

Task contextLink to this heading

class TaskContextLink to this definition

Contains context for the running Task. Context only passed to a Task if it was defined with takes_context=True.

Attributes of TaskContext cannot be modified.

task_resultLink to this definition

The TaskResult currently being run.

attemptLink to this definition

The number of the current execution attempts for this Task, starting at 1.

Task resultsLink to this heading

class TaskResultStatusLink to this definition

An Enum representing the status of a TaskResult.

READYLink to this definition

The Task has just been enqueued, or is ready to be executed again.

RUNNINGLink to this definition

The Task is currently being executed.

FAILEDLink to this definition

The Task raised an exception during execution, or was unable to start.

SUCCESSFULLink to this definition

The Task has finished executing successfully.

class TaskResultLink to this definition

The TaskResult stores the information about a specific execution of a Task.

Attributes of TaskResult cannot be modified.

taskLink to this definition

The Task the result was enqueued for.

idLink to this definition

A unique identifier for the result, which can be passed to Task.get_result().

The format of the id will depend on the backend being used. Task result ids are always strings less than 64 characters.

See Task results for more details.

statusLink to this definition

The status of the result.

enqueued_atLink to this definition

The time when the Task was enqueued.

started_atLink to this definition

The time when the Task began execution, on its first attempt.

last_attempted_atLink to this definition

The time when the most recent Task run began execution.

finished_atLink to this definition

The time when the Task finished execution, whether it failed or succeeded.

backendLink to this definition

The backend the result is from.

errorsLink to this definition

A list of TaskError instances for the errors raised as part of each execution of the Task.

return_valueLink to this definition

The return value from the Task function.

If the Task did not finish successfully, ValueError is raised.

See return values for usage examples.

refresh()Link to this definition

Refresh the result’s attributes from the queue store.

arefresh()Link to this definition

The async variant of TaskResult.refresh().

is_finishedLink to this definition

Whether the Task has finished (successfully or not).

attemptsLink to this definition

The number of times the Task has been run.

If the task is currently running, it does not count as an attempt.

worker_idsLink to this definition

The ids of the workers which have executed the Task.

Task errorsLink to this heading

class TaskErrorLink to this definition

Contains information about the error raised during the execution of a Task.

tracebackLink to this definition

The traceback (as a string) from the raised exception when the Task failed.

exception_classLink to this definition

The exception class raised when executing the Task.

BackendsLink to this heading

Backends handle how Tasks are stored and executed. All backends share a common interface defined by BaseTaskBackend, which specifies the core methods for enqueueing Tasks and retrieving results.

Base backendLink to this heading

class BaseTaskBackendLink to this definition

BaseTaskBackend is the parent class for all Task backends.

optionsLink to this definition

A dictionary of extra parameters for the Task backend. These are provided using the OPTIONS setting.

enqueue(task, args, kwargs)Link to this definition

Task backends which subclass BaseTaskBackend should implement this method as a minimum.

When implemented, enqueue() enqueues the task, a Task instance, for later execution. args are the positional arguments and kwargs are the keyword arguments to be passed to the task. Returns a TaskResult.

aenqueue(task, args, kwargs)Link to this definition

The async variant of BaseTaskBackend.enqueue().

get_result(result_id)Link to this definition

Retrieve a result by its id. If the result does not exist, TaskResultDoesNotExist is raised.

If the backend does not support get_result(), NotImplementedError is raised.

aget_result(result_id)Link to this definition

The async variant of BaseTaskBackend.get_result().

validate_task(task)Link to this definition

Validates whether the provided Task is able to be enqueued using the backend. If the Task is not valid, InvalidTask is raised.

Feature flagsLink to this heading

Some backends may not support all features Django provides. It’s possible to identify the supported functionality of a backend, and potentially change behavior accordingly.

BaseTaskBackend.supports_deferLink to this definition

Whether the backend supports enqueueing Tasks to be executed after a specific time using the run_after attribute.

BaseTaskBackend.supports_async_taskLink to this definition

Whether the backend supports enqueueing async functions (coroutines).

BaseTaskBackend.supports_get_resultLink to this definition

Whether the backend supports retrieving Task results from another thread after they have been enqueued.

BaseTaskBackend.supports_priorityLink to this definition

Whether the backend supports executing Tasks as ordered by their priority.

The below table notes which of the built-in backends support which features:

Available backendsLink to this heading

Django includes only development and testing backends. These support local execution and inspection, for production ready backends refer to Configuring a Task backend.

Immediate backendLink to this heading

class ImmediateBackendLink to this definition

The immediate backend executes Tasks immediately, rather than in the background.

더미 백엔드Link to this heading

class DummyBackendLink to this definition

The dummy backend does not execute enqueued Tasks. Instead, it stores task results for later inspection.

resultsLink to this definition

A list of results for the enqueued Tasks, in the order they were enqueued.

clear()Link to this definition

Clears the list of stored results.

예외Link to this heading

exception InvalidTaskLink to this definition

Raised when the Task attempting to be enqueued is invalid.

exception InvalidTaskBackendLink to this definition

Raised when the requested BaseTaskBackend is invalid.

exception TaskResultDoesNotExistLink to this definition

Raised by get_result() when the provided result_id does not exist.

exception TaskResultMismatchLink to this definition

Raised by get_result() when the provided result_id is for a different Task than the current Task.

Footnotes