Task Messages

• Message format
• Example message

• id

  Unique id of the task (UUID). required

• args

  list:

  List of arguments. Will be an empty list if not provided.

• kwargs

  dictionary:

  Dictionary of keyword arguments. Will be an empty dictionary if not provided.

• retries

  int:

  Current number of times this task has been retried. Defaults to 0 if not specified.

• eta

  Estimated time of arrival. This is the date and time in ISO 8601 format. If not provided the message is not scheduled, but will be executed asap.

• string (ISO 8601):

  2.0.2 新版功能.

  Expiration date. This is the date and time in ISO 8601 format. If not provided the message will never expire. The message will be expired when the message is received and the expiration date has been exceeded.

Extensions are additional keys in the message body that the worker may or may not support. If the worker finds an extension key it doesn’t support it should optimally reject the message so another worker gets a chance to process it.

• taskset

  string:

  The taskset this task is part of (if any).

• chord

  subtask:

  2.3 新版功能.

  Signifies that this task is one of the header parts of a chord. The value of this key is the body of the cord that should be executed when all of the tasks in the header has returned.

• 3.0 新版功能.

  A list of subtasks to apply if the task exited successfully.

• errbacks

  <list>subtask:

  3.0 新版功能.

  A list of subtasks to apply if an error occurs while executing the task.

• timelimit

  <tuple>(float, float):

  3.1 新版功能.

  Task execution time limit settings. This is a tuple of hard and soft time limit value (int/float or None for no limit).

  Example value specifying a soft time limit of 3 seconds, and a hard time limt of 10 seconds:

This is an example invocation of the celery.task.PingTask task in JSON format:

 "task": "celery.task.PingTask",
 "kwargs": {},

Several types of serialization formats are supported using the content_type message header.