decorators in combination with the task decorator you must make sure that the task decorator is applied last (which in Python oddly means that it must be the first in the list): @app.task @decorator2 Celery supports linking tasks together so that one task follows another. The callback task will be applied with the result of the parent task as a partial argument: add.apply_async((2, 2), link=add.s(16)) the previous result, forming the expression (2 + 2) + 16 = 20 You can also cause a callback to be applied if task raises an exception (errback), but this behaves differently from a regular callback in that

decorators in combination with the task decorator you must make sure that the task decorator is applied last (which in Python oddly means that it must be the first in the list): @app.task @decorator2 Celery supports linking tasks together so that one task follows another. The callback task will be applied with the result of the parent task as a partial argument: add.apply_async((2, 2), link=add.s(16)) that adds 16 to the previous result, forming the expression You can also cause a callback to be applied if task raises an exception (errback), but this behaves differently from a regular callback in that

decorators in combination with the task decorator you must make sure that the task decorator is applied last (oddly, in Python this means it must be first in the list): @app.task @decorator2 @decorator1 Celery supports linking tasks together so that one task follows another. The callback task will be applied with the result of the parent task as a partial argument: add.apply_async((2, 2), link=add.s(16)) the previous result, forming the expression (2 + 2) + 16 = 20 You can also cause a callback to be applied if task raises an exception (errback), but this behaves differently from a regular callback in that

decorators in combination with the task decorator you must make sure that the task decorator is applied last (oddly, in Python this means it must be first in the list): @app.task @decorator2 @decorator1 Celery supports linking tasks together so that one task follows another. The callback task will be applied with the result of the parent task as a partial argument: add.apply_async((2, 2), link=add.s(16)) that adds 16 to the previous result, forming the expression You can also cause a callback to be applied if task raises an exception (errback), but this behaves differently from a regular callback in that

decorators in combination with the task decorator you must make sure that the task decorator is applied last (oddly, in Python this means it must be first in the list): @app.task @decorator2 @decorator1 Celery supports linking tasks together so that one task follows another. The callback task will be applied with the result of the parent task as a partial argument: add.apply_async((2, 2), link=add.s(16)) that adds 16 to the previous result, forming the expression You can also cause a callback to be applied if task raises an exception (errback), but this behaves differently from a regular callback in that

decorators in combination with the task decorator you must make sure that the task decorator is applied last (oddly, in Python this means it must be first in the list): @app.task @decorator2 @decorator1 Celery supports linking tasks together so that one task follows another. The callback task will be applied with the result of the parent task as a partial argument: add.apply_async((2, 2), link=add.s(16)) the previous result, forming the expression (2 + 2) + 16 = 20 You can also cause a callback to be applied if task raises an exception (errback), but this behaves differently from a regular callback in that

decorators in combination with the task decorator you must make sure that the task decorator is applied last (oddly, in Python this means it must be first in the list): @app.task @decorator2 @decorator1 Celery supports linking tasks together so that one task follows another. The callback task will be applied with the result of the parent task as a partial argument: add.apply_async((2, 2), link=add.s(16)) the previous result, forming the expression (2 + 2) + 16 = 20 You can also cause a callback to be applied if task raises an exception (errback), but this behaves differently from a regular callback in that

decorators in combination with the task decorator you must make sure that the task decorator is applied last (oddly, in Python this means it must be first in the list): @app.task @decorator2 @decorator1 Celery supports linking tasks together so that one task follows another. The callback task will be applied with the result of the parent task as a partial argument: add.apply_async((2, 2), link=add.s(16)) that adds 16 to the previous result, forming the expression You can also cause a callback to be applied if task raises an exception (errback), but this behaves differently from a regular callback in that

decorators in combination with the task decorator you must make sure that the task decorator is applied last (oddly, in Python this means it must be first in the list): @app.task @decorator2 @decorator1 Celery supports linking tasks together so that one task follows another. The callback task will be applied with the result of the parent task as a partial argument: add.apply_async((2, 2), link=add.s(16)) the previous result, forming the expression (2 + 2) + 16 = 20 You can also cause a callback to be applied if task raises an exception (errback), but this behaves differently from a regular callback in that

decorators in combination with the task decorator you must make sure that the task decorator is applied last (oddly, in Python this means it must be first in the list): @app.task @decorator2 @decorator1 Celery supports linking tasks together so that one task follows another. The callback task will be applied with the result of the parent task as a partial argument: add.apply_async((2, 2), link=add.s(16)) the previous result, forming the expression (2 + 2) + 16 = 20 You can also cause a callback to be applied if task raises an exception (errback), but this behaves differently from a regular callback in that