objects for groups in the Redis backend. This can cause those results to be be returned in a different order to their associated tasks in the original group instantiation. Celery 4.4.7 and up introduce an opt-in opt-in behaviour which fixes this issue and ensures that group results are returned in the same order the tasks were defined, matching the behaviour of other backends. This change is incompatible with if the task failed, to get the exception and traceback). Results are not enabled by default. In order to do remote procedure calls or keep track of task results in a database, you will need to configure

if the task failed, to get the exception and traceback). Results are not enabled by default. In order to do remote procedure calls or keep track of task results in a database, you will need to configure If only a package name is specified, it’ll try to search for the app instance, in the following order: With --app=proj: 1. an attribute named proj.app, or 2. an attribute named proj.celery, or 3. any special result instance that lets you inspect the results as a group, and retrieve the return values in order. >>> from celery import group >>> from proj.tasks import add >>> group(add.s(i, i) for i in range(10))()

if the task failed, to get the exception and traceback). Results are not enabled by default. In order to do remote procedure calls or keep track of task results in a database, you will need to configure If only a package name is specified, it’ll try to search for the app instance, in the following order: With --app=proj: 1. an attribute named proj.app, or 2. an attribute named proj.celery, or 3. any special result instance that lets you inspect the results as a group, and retrieve the return values in order. >>> from celery import group >>> from proj.tasks import add >>> group(add.s(i, i) for i in range(10))()

if the task failed, to get the exception and traceback). Results are not enabled by default. In order to do remote procedure calls or keep track of task results in a database, you will need to configure If only a package name is specified, it’ll try to search for the app instance, in the following order: With --app=proj: 1. an attribute named proj.app, or 2. an attribute named proj.celery, or 3. any special result instance that lets you inspect the results as a group, and retrieve the return values in order. >>> from celery import group >>> from proj.tasks import add >>> group(add.s(i, i) for i in range(10))()

if the task failed, to get the exception and traceback). Results are not enabled by default. In order to do remote procedure calls or keep track of task results in a database, you will need to configure If only a package name is specified, it’ll try to search for the app instance, in the following order: With --app=proj: 1. an attribute named proj.app, or 2. an attribute named proj.celery, or 3. any special result instance that lets you inspect the results as a group, and retrieve the return values in order. >>> from celery import group >>> from proj.tasks import add >>> group(add.s(i, i) for i in range(10))()

objects for groups in the Redis backend. This can cause those results to be be returned in a different order to their associated tasks in the original group instantiation. Celery 4.4.7 introduced an opt-in behaviour behaviour which fixes this issue and ensures that group results are returned in the same order the tasks were defined, matching the behaviour of other backends. In Celery 5.0 this behaviour was changed if the task failed, to get the exception and traceback). Results are not enabled by default. In order to do remote procedure calls or keep track of task results in a database, you will need to configure

objects for groups in the Redis backend. This can cause those results to be be returned in a different order to their associated tasks in the original group instantiation. Celery 4.4.7 introduced an opt-in behaviour behaviour which fixes this issue and ensures that group results are returned in the same order the tasks were defined, matching the behaviour of other backends. In Celery 5.0 this behaviour was changed if the task failed, to get the exception and traceback). Results are not enabled by default. In order to do remote procedure calls or keep track of task results in a database, you will need to configure

objects for groups in the Redis backend. This can cause those results to be be returned in a different order to their associated tasks in the original group instantiation. Celery 4.4.7 introduced an opt-in behaviour behaviour which fixes this issue and ensures that group results are returned in the same order the tasks were defined, matching the behaviour of other backends. In Celery 5.0 this behaviour was changed if the task failed, to get the exception and traceback). Results are not enabled by default. In order to do remote procedure calls or keep track of task results in a database, you will need to configure

objects for groups in the Redis backend. This can cause those results to be be returned in a different order to their associated tasks in the original group instantiation. Celery 4.4.7 introduced an opt-in behaviour behaviour which fixes this issue and ensures that group results are returned in the same order the tasks were defined, matching the behaviour of other backends. In Celery 5.0 this behaviour was changed if the task failed, to get the exception and traceback). Results are not enabled by default. In order to do remote procedure calls or keep track of task results in a database, you will need to configure

if the task failed, to get the exception and traceback). Results are not enabled by default. In order to do remote procedure calls or keep track of task results in a database, you will need to configure only a package name is specified, where it’ll try to search for the app instance, in the following order: With --app=proj: 3.2. Getting Started 31 Celery Documentation, Release 4.4.2 1) an attribute special result instance that lets you inspect the results as a group, and retrieve the return values in order. 3.2. Getting Started 35 Celery Documentation, Release 4.4.2 >>> from celery import group >>> from