Name of the executing task. • task_retries How many times the current task has been retried. An integer starting at 0. • task_is_eager Set to True if the task is executed locally in the client, and not period of time is the task allowed to run. If this is None no rate limit is in effect. If it is an integer, it is interpreted as “tasks per second”. The rate limits can be specified in seconds, minutes or specified date and time has passed, but not necessarily at that exact time. While countdown is an integer, eta must be a datetime object, specifying an exact date and time in the future. This is good if

Name of the executing task. task_retries How many times the current task has been retried. An integer starting at 0. task_is_eager Set to True if the task is executed locally in the client, and not period of time is the task allowed to run. If this is None no rate limit is in effect. If it is an integer, it is interpreted as “tasks per second”. The rate limits can be specified in seconds, minutes or specified date and time has passed, but not necessarily at that exact time. While countdown is an integer, eta must be a datetime object, specifying an exact date and time in the future. This is good if

Name of the executing task. • task_retries How many times the current task has been retried. An integer starting at 0. • task_is_eager Set to True if the task is executed locally in the client, and not period of time is the task allowed to run. If this is None no rate limit is in effect. If it is an integer, it is interpreted as “tasks per second”. The rate limits can be specified in seconds, minutes or specified date and time has passed, but not necessarily at that exact time. While countdown is an integer, eta must be a datetime object, specifying an exact date and time in the future. This is good if

Name of the executing task. task_retries How many times the current task has been retried. An integer starting at 0. task_is_eager Set to True if the task is executed locally in the client, and not period of time is the task allowed to run. If this is None no rate limit is in effect. If it is an integer, it is interpreted as “tasks per second”. The rate limits can be specified in seconds, minutes or specified date and time has passed, but not necessarily at that exact time. While countdown is an integer, eta must be a datetime object, specifying an exact date and time in the future. This is good if

arguments. kwargs Keyword arguments. retries How many times the current task has been retried. An integer starting at 0. is_eager Set to True if the task is executed locally in the client, and not by a period of time is the task allowed to run. If this is None no rate limit is in effect. If it is an integer, it is interpreted as “tasks per second”. The rate limits can be specified in seconds, minutes or alerts, so appropriate action can be taken to ease the workload. See Munin. While countdown is an integer, eta must be a datetime object, specifying an exact date and time (including mil- lisecond precision

arguments. kwargs Keyword arguments. retries How many times the current task has been retried. An integer starting at 0. is_eager Set to True if the task is executed locally in the client, and not by a period of time is the task allowed to run. If this is None no rate limit is in effect. If it is an integer, it is interpreted as “tasks per second”. The rate limits can be specified in seconds, minutes or alerts, so appropriate action can be taken to ease the workload. See Munin. While countdown is an integer, eta must be a datetime object, specifying an exact date and time (including mil- lisecond precision

the currently executing task. task_retries How many times the current task has been retried. An integer starting at 0. is_eager Set to True if the task is executed locally in the client, and not by a period of time is the task allowed to run. If this is None no rate limit is in effect. If it is an integer, it is interpreted as “tasks per second”. The rate limits can be specified in seconds, minutes or alerts, so appropriate action can be taken to ease the workload. See Munin. While countdown is an integer, eta must be a datetime object, specifying an exact date and time (including millisecond precision

arguments. kwargs: Keyword arguments. retries: How many times the current task has been retried. An integer starting at 0. is_eager: Set to True if the task is executed locally in the client, and not by a period of time is the task allowed to run. If this is None no rate limit is in effect. If it is an integer, it is interpreted as “tasks per second”. The rate limits can be specified in seconds, minutes or alerts, so appropriate action can be taken to ease the workload. See Munin. While countdown is an integer, eta must be a datetime object, specifying an exact date and time (including millisecond precision

Celery Documentation, Release 4.0.0 retries How many times the current task has been retried. An integer starting at 0. is_eager Set to True if the task is executed locally in the client, not by a worker some time before it’s allowed to start. If this is None no rate limit is in effect. If it is an integer or float, it is interpreted as “tasks per second”. The rate limits can be specified in seconds, alerts, so appropriate action can be taken to ease the workload. See Munin. While countdown is an integer, eta must be a datetime object, specifying an exact date and time (including mil- lisecond precision

Name of host that sent this task. retries: How many times the current task has been retried. An integer starting at 0. is_eager: Set to True if the task is executed locally in the client, not by a worker some time before it’s allowed to start. If this is None no rate limit is in effect. If it is an integer or float, it is interpreted as “tasks per second”. The rate limits can be specified in seconds, alerts, so appropriate action can be taken to ease the workload. See Munin. While countdown is an integer, eta must be a datetime [https://docs.python.org/dev/library/datetime.html#datetime.datetime] object