and repeated tasks • Encrypted and compressed packages • Failure and success database or cache • Result hooks, groups and chains • Django Admin integration • PaaS compatible with multiple instances tested against Django version 1.8.8 and 1.9.1. • Django-picklefield Used to store args, kwargs and result objects in the database. • Arrow The scheduler uses Chris Smith’s wonderful project to determine already using django-redis for your caching, you can take advantage of its excellent connection backend by supplying the name of the cache connection you want to use instead of a direct Redis connection:

and repeated tasks • Encrypted and compressed packages • Failure and success database or cache • Result hooks, groups and chains • Django Admin integration • PaaS compatible with multiple instances tested against Django version 1.8.8 and 1.9.1. • Django-picklefield Used to store args, kwargs and result objects in the database. • Arrow The scheduler uses Chris Smith’s wonderful project to determine already using django-redis for your caching, you can take advantage of its excellent connection backend by supplying the name of the cache connection you want to use instead of a direct Redis connection:

and repeated tasks • Encrypted and compressed packages • Failure and success database or cache • Result hooks, groups and chains • Django Admin integration • PaaS compatible with multiple instances tested against Django version 1.7.10 and 1.8.5. • Django-picklefield Used to store args, kwargs and result objects in the database. • Arrow The scheduler uses Chris Smith’s wonderful project to determine already using django-redis for your caching, you can take advantage of its excellent connection backend by supplying the name of the cache connection you want to use instead of a direct Redis connection:

and repeated tasks • Encrypted and compressed packages • Failure and success database or cache • Result hooks, groups and chains • Django Admin integration • PaaS compatible with multiple instances tested against Django version 1.8.12 and 1.9.5. • Django-picklefield Used to store args, kwargs and result objects in the database. • Arrow The scheduler uses Chris Smith’s wonderful project to determine already using django-redis for your caching, you can take advantage of its excellent connection backend by supplying the name of the cache connection you want to use instead of a direct Redis connection:

and repeated tasks • Encrypted and compressed packages • Failure and success database or cache • Result hooks, groups and chains • Django Admin integration • PaaS compatible with multiple instances tested against Django version 1.8.8 and 1.9.1. • Django-picklefield Used to store args, kwargs and result objects in the database. • Arrow The scheduler uses Chris Smith’s wonderful project to determine already using django-redis for your caching, you can take advantage of its excellent connection backend by supplying the name of the cache connection you want to use instead of a direct Redis connection:

and repeated tasks • Encrypted and compressed packages • Failure and success database or cache • Result hooks, groups and chains • Django Admin integration • PaaS compatible with multiple instances tested against Django version 1.8.8 and 1.9.1. • Django-picklefield Used to store args, kwargs and result objects in the database. • Arrow The scheduler uses Chris Smith’s wonderful project to determine already using django-redis for your caching, you can take advantage of its excellent connection backend by supplying the name of the cache connection you want to use instead of a direct Redis connection:

and repeated tasks • Encrypted and compressed packages • Failure and success database or cache • Result hooks, groups and chains • Django Admin integration • PaaS compatible with multiple instances tested against Django version 1.8.13 and 1.9.7. • Django-picklefield Used to store args, kwargs and result objects in the database. • Arrow The scheduler uses Chris Smith’s wonderful project to determine already using django-redis for your caching, you can take advantage of its excellent connection backend by supplying the name of the cache connection you want to use instead of a direct Redis connection:

and repeated tasks • Encrypted and compressed packages • Failure and success database or cache • Result hooks, groups and chains • Django Admin integration • PaaS compatible with multiple instances tested against Django version 1.8.11 and 1.9.4. • Django-picklefield Used to store args, kwargs and result objects in the database. • Arrow The scheduler uses Chris Smith’s wonderful project to determine already using django-redis for your caching, you can take advantage of its excellent connection backend by supplying the name of the cache connection you want to use instead of a direct Redis connection:

and repeated tasks • Encrypted and compressed packages • Failure and success database or cache • Result hooks, groups and chains • Django Admin integration • PaaS compatible with multiple instances Django versions 1.8.18 LTS, 1.11.9 and 2.0. • Django-picklefield Used to store args, kwargs and result objects in the database. • Arrow The scheduler uses Chris Smith’s wonderful project to determine already using django-redis for your caching, you can take advantage of its excellent connection backend by supplying the name of the cache connection you want to use instead of a direct Redis connection:

and repeated tasks • Encrypted and compressed packages • Failure and success database or cache • Result hooks, groups and chains • Django Admin integration • PaaS compatible with multiple instances Django versions 1.8.18 LTS, 1.10.7 and 1.11. • Django-picklefield Used to store args, kwargs and result objects in the database. • Arrow The scheduler uses Chris Smith’s wonderful project to determine already using django-redis for your caching, you can take advantage of its excellent connection backend by supplying the name of the cache connection you want to use instead of a direct Redis connection: