that inherits from Task. The best practice is to only create custom task classes when you want to change generic behavior, and use the decorator to define tasks. See also: The full documentation on how Chapter 1. Getting Started Celery Documentation, Release 2.5.5 Right now we have to check the worker log files to know what happened with the task. Applying a task returns an AsyncResult, if you have configured client, and not by a worker. logfile The file the worker logs to. See Logging. loglevel The current log level used. hostname Hostname of the worker instance executing the task. delivery_info Additional

task fails • get a list of people and companies using Celery • write my own remote control command • change worker queues at runtime Jump to • Brokers • Applications • Tasks • Calling 2.2. Getting Started subscribe to worker related events: BROKER_TRANSPORT_OPTIONS = {'fanout_patterns': True} Note that this change is backward incompatible so all workers in the cluster must have this option enabled, or else they ironcache: ironcache:://project_id:token@ This will default to a cache named “Celery”, if you want to change that: ironcache:://project_id:token@/awesomecache More Information You can find more information

Configuration and defaults Django Contributing Community Resources Tutorials Frequently Asked Questions Change history What’s new in Celery 3.1 (Cipater) What’s new in Celery 3.0 (Chiastic Slide) What’s new in a task fails get a list of people and companies using Celery write my own remote control command change worker queues at runtime Jump to ⟶ Brokers Workers Security Contributing Applications Tasks Calling subscribe to worker related events: BROKER_TRANSPORT_OPTIONS = {'fanout_patterns': True} Note that this change is backward incompatible so all workers in the cluster must have this option enabled, or else they

Configuration and defaults Django Contributing Community Resources Tutorials Frequently Asked Questions Change history What’s new in Celery 4.0 (latentcall) What’s new in Celery 3.1 (Cipater) API Reference Internals configuration settings get a list of people and companies using Celery write my own remote control command change worker queues at runtime Jump to ⟶ Brokers Applications Tasks Calling Workers Daemonizing Monitoring worker related events: app.conf.broker_transport_options = {'fanout_patterns': True} Note that this change is backward incompatible so all workers in the cluster must have this option enabled, or else they

that inherits from Task. The best practice is to only create custom task classes when you want to change generic behavior, and use the decorator to define tasks. See also: The full documentation on how the task until a worker server has consumed and executed it. Right now we have to check the worker log files to know what happened with the task. Applying a task returns an AsyncResult, if you have configured client, and not by a worker. logfile The file the worker logs to. See Logging. loglevel The current log level used. hostname Hostname of the worker instance executing the task. delivery_info Additional

Documenting Tasks with Sphinx Django Contributing Community Resources Tutorials Frequently Asked Questions Change history What’s new in Celery 4.4 (Cliffs) API Reference Internals History Glossary Indices and tables current task get a list of people and companies using Celery write my own remote control command change worker queues at runtime Jump to ⟶ Brokers Applications Tasks Calling Workers Daemonizing Monitoring worker related events: app.conf.broker_transport_options = {'fanout_patterns': True} Note that this change is backward incompatible so all workers in the cluster must have this option enabled, or else they

Documenting Tasks with Sphinx Django Contributing Community Resources Tutorials Frequently Asked Questions Change history What’s new in Celery 4.4 (Cliffs) API Reference Internals History Glossary Indices and tables current task get a list of people and companies using Celery write my own remote control command change worker queues at runtime Jump to ⟶ Brokers Applications Tasks Calling Workers Daemonizing Monitoring worker related events: app.conf.broker_transport_options = {'fanout_patterns': True} Note that this change is backward incompatible so all workers in the cluster must have this option enabled, or else they

Documenting Tasks with Sphinx Django Contributing Community Resources Tutorials Frequently Asked Questions Change history What’s new in Celery 4.4 (Cliffs) API Reference Internals History Glossary Indices and tables current task get a list of people and companies using Celery write my own remote control command change worker queues at runtime Jump to ⟶ Brokers Applications Tasks Calling Workers Daemonizing Monitoring worker related events: app.conf.broker_transport_options = {'fanout_patterns': True} Note that this change is backward incompatible so all workers in the cluster must have this option enabled, or else they

Documenting Tasks with Sphinx Django Contributing Community Resources Tutorials Frequently Asked Questions Change history What’s new in Celery 4.4 (Cliffs) API Reference Internals History Glossary Indices and tables current task get a list of people and companies using Celery write my own remote control command change worker queues at runtime Jump to ⟶ Brokers Applications Tasks Calling Workers Daemonizing Monitoring worker related events: app.conf.broker_transport_options = {'fanout_patterns': True} Note that this change is backward incompatible so all workers in the cluster must have this option enabled, or else they

Documenting Tasks with Sphinx Django Contributing Community Resources Tutorials Frequently Asked Questions Change history What’s new in Celery 4.4 (Cliffs) API Reference Internals History Glossary Indices and tables current task get a list of people and companies using Celery write my own remote control command change worker queues at runtime Jump to ⟶ Brokers Applications Tasks Calling Workers Daemonizing Monitoring returned in the same order the tasks were defined, matching the behaviour of other backends. This change is incompatible with workers running versions of Celery without this feature, so the feature must