result backend is disabled for any task (header or body) in your chord you should read “Important Notes.” Chords are not currently supported with the RPC result backend. A chord is a task that only executes s(i, i) for i in range(10)) | ... xsum.s().on_error(on_chord_error.s())).delay() Important Notes Tasks used within a chord must not ignore their results. In practice this means that you must enable worker instance being killed abruptly, so this also means the task must be idempotent See also Notes at Should I use retry or acks_late?. [*] [†] [‡] You can enable this behavior by using the following

result backend is disabled for any task (header or body) in your chord you should read “Important Notes.” Chords are not currently supported with the RPC result backend. A chord is a task that only executes s(i, i) for i in range(10)) | ... xsum.s().on_error(on_chord_error.s())).delay() Important Notes Tasks used within a chord must not ignore their results. In practice this means that you must enable worker instance being killed abruptly, so this also means the task must be idempotent See also Notes at Should I use retry or acks_late?. [*] [†] [‡] You can enable this behavior by using the following

result backend is disabled for any task (header or body) in your chord you should read “Important Notes.” Chords are not currently supported with the RPC result backend. A chord is a task that only executes s(i, i) for i in range(10)) | ... xsum.s().on_error(on_chord_error.s())).delay() Important Notes Tasks used within a chord must not ignore their results. In practice this means that you must enable worker instance being killed abruptly, so this also means the task must be idempotent See also Notes at Should I use retry or acks_late?. [*] [†] [‡] You can enable this behavior by using the following

result backend is disabled for any task (header or body) in your chord you should read “Important Notes.” Chords are not currently supported with the RPC result backend. A chord is a task that only executes s(i, i) for i in range(10)) | ... xsum.s().on_error(on_chord_error.s())).delay() Important Notes Tasks used within a chord must not ignore their results. In practice this means that you must enable worker instance being killed abruptly, so this also means the task must be idempotent See also Notes at Should I use retry or acks_late?. [*] [†] [‡] You can enable this behavior by using the following

result backend is disabled for any task (header or body) in your chord you should read “Important Notes.” Chords are not currently supported with the RPC result backend. A chord is a task that only executes s(i, i) for i in range(10)) | ... xsum.s().on_error(on_chord_error.s())).delay() Important Notes Tasks used within a chord must not ignore their results. In practice this means that you must enable worker instance being killed abruptly, so this also means the task must be idempotent See also Notes at Should I use retry or acks_late?. [*] [†] [‡] You can enable this behavior by using the following

result backend is disabled for any task (header or body) in your chord you should read “Important Notes.” Chords are not currently supported with the RPC result backend. A chord is a task that only executes s(i, i) for i in range(10)) | ... xsum.s().on_error(on_chord_error.s())).delay() Important Notes Tasks used within a chord must not ignore their results. In practice this means that you must enable worker instance being killed abruptly, so this also means the task must be idempotent See also Notes at Should I use retry or acks_late?. You can enable this behavior by using the following configuration

result backend is disabled for any task (header or body) in your chord you should read “Important Notes.” Chords are not currently supported with the RPC result backend. A chord is a task that only executes s(i, i) for i in range(10)) | ... xsum.s().on_error(on_chord_error.s())).delay() Important Notes Tasks used within a chord must not ignore their results. In practice this means that you must enable worker instance being killed abruptly, so this also means the task must be idempotent See also Notes at Should I use retry or acks_late?. You can enable this behavior by using the following configuration

result backend is disabled for any task (header or body) in your chord you should read “Important Notes.” Chords are not currently supported with the RPC result backend. A chord is a task that only executes s(i, i) for i in range(10)) | ... xsum.s().on_error(on_chord_error.s())).delay() Important Notes Tasks used within a chord must not ignore their results. In practice this means that you must enable worker instance being killed abruptly, so this also means the task must be idempotent See also Notes at Should I use retry or acks_late?. You can enable this behavior by using the following configuration

result backend is disabled for any task (header or body) in your chord you should read “Important Notes.” Chords are not currently supported with the RPC result backend. A chord is a task that only executes s(i, i) for i in range(10)) | ... xsum.s().on_error(on_chord_error.s())).delay() Important Notes Tasks used within a chord must not ignore their results. In practice this means that you must enable worker instance being killed abruptly, so this also means the task must be idempotent See also Notes at Should I use retry or acks_late?. You can enable this behavior by using the following configuration

result backend is disabled for any task (header or body) in your chord you should read “Important Notes.” Chords are not currently supported with the RPC result backend. A chord is a task that only executes s(i, i) for i in range(10)) | ... xsum.s().on_error(on_chord_error.s()))).delay() Important Notes Tasks used within a chord must not ignore their results. In practice this means that you must enable worker instance being killed abruptly, so this also means the task must be idempotent See also Notes at Should I use retry or acks_late?. You can enable this behavior by using the following configuration