functions. Instead of a bool this can also be set to the number of seconds you want the cache to retain results. e.g. cached=60 #### 1.2.26 scheduler You can disable the scheduler by setting this option to False processed. • In case a task is worked on twice, the task result will be updated with the latest results. • In some rare cases a non-atomic broker will re-queue a task after it has been acknowledged. g. cached=60. Especially useful with large and group operations where you don't need the all results in your database and want to take advantage of the speed of your cache backend. ## broker A broker

functions. Instead of a bool this can also be set to the number of seconds you want the cache to retain results. e.g. cached=60 ## scheduler You can disable the scheduler by setting this option to False. This processed. • In case a task is worked on twice, the task result will be updated with the latest results. • In some rare cases a non-atomic broker will re-queue a task after it has been acknowledged. g. cached=60. Especially useful with large and group operations where you don't need the all results in your database and want to take advantage of the speed of your cache backend. ## broker A broker

functions. Instead of a bool this can also be set to the number of seconds you want the cache to retain results. e.g. cached=60 ## scheduler You can disable the scheduler by setting this option to False. This processed. - In case a task is worked on twice, the task result will be updated with the latest results. - In some rare cases a non-atomic broker will re-queue a task after it has been acknowledged. e.g. cached=60. Especially useful with large and group operations where you don’t need the all results in your database and want to take advantage of the speed of your cache backend. ## broker A broker

functions. Instead of a bool this can also be set to the number of seconds you want the cache to retain results. e.g. cached=60 #### 1.2.24 scheduler You can disable the scheduler by setting this option to False processed. • In case a task is worked on twice, the task result will be updated with the latest results. • In some rare cases a non-atomic broker will re-queue a task after it has been acknowledged. • g. cached=60. Especially useful with large and group operations where you don't need the all results in your database and want to take advantage of the speed of your cache backend. ## broker A broker

functions. Instead of a bool this can also be set to the number of seconds you want the cache to retain results. e.g. cached=60 #### 1.2.28 scheduler You can disable the scheduler by setting this option to False processed. • In case a task is worked on twice, the task result will be updated with the latest results. • In some rare cases a non-atomic broker will re-queue a task after it has been acknowledged. g. cached=60. Especially useful with large and group operations where you don't need the all results in your database and want to take advantage of the speed of your cache backend. ## broker A broker

functions. Instead of a bool this can also be set to the number of seconds you want the cache to retain results. e.g. cached=60 #### 1.2.24 scheduler You can disable the scheduler by setting this option to False g. cached=60. Especially useful with large and group operations where you don't need the all results in your database and want to take advantage of the speed of your cache backend. ## broker A broker run() $ it again to retrieve a new result. #### 1.4.3 Cached operations You can run your tasks results against the Django cache backend instead of the database backend by either using the global cached

functions. Instead of a bool this can also be set to the number of seconds you want the cache to retain results. e.g. cached=60 ## scheduler You can disable the scheduler by setting this option to False. This g. cached=60. Especially useful with large and group operations where you don't need the all results in your database and want to take advantage of the speed of your cache backend. ## broker A broker Async.run() $ . it again to retrieve a new result. ## Cached operations You can run your tasks results against the Django cache backend instead of the database backend by either using the global cached

functions. Instead of a bool this can also be set to the number of seconds you want the cache to retain results. e.g. cached=60 ## scheduler You can disable the scheduler by setting this option to False. This g. cached=60. Especially useful with large and group operations where you don't need the all results in your database and want to take advantage of the speed of your cache backend. ## broker A broker Async.run() $ . it again to retrieve a new result. ## Cached operations You can run your tasks results against the Django cache backend instead of the database backend by either using the global cached

functions. Instead of a bool this can also be set to the number of seconds you want the cache to retain results. e.g. cached=60 ## scheduler You can disable the scheduler by setting this option to False. This processed. - In case a task is worked on twice, the task result will be updated with the latest results. - In some rare cases a non-atomic broker will re-queue a task after it has been acknowledged. g. cached=60. Especially useful with large and group operations where you don't need the all results in your database and want to take advantage of the speed of your cache backend. ## broker A broker