Task name and positional arguments don't appear in the results

[ddahan]

No matter how I run a task, I can't get the task name nor the parameters display in the results:

Here is my task (I tried with bind=True too):

@app.task(name="core.add")
def add(x, y):
    return x + y

To run the task, I tried:

• In a shell: add.delay(2, 10)
• In a shell: add.apply_async(args=[2, 10])
• Using django-celery-beat, setting a new PeriodicTask object with position arguments set to [2, 10]

Same issue every time. What did I do wrong? Thanks.

[cuiliang0302]

me too

[cuiliang0302]

There is no problem with the replacement version 2.3.1

[auvipy]

v2.4.0 released and v2.4.1 is coming

[auvipy]

@AmitPhulera can you please verify the regression?

[valberg]

We are experiencing the same issues after upgrading to 2.4.0

[auvipy]

We are experiencing the same issues after upgrading to 2.4.0

can you please check which commit created the regression? there is only two to check

[auvipy]

is it https://github.com/celery/django-celery-results/commit/ad508fe3433499e5fc94645412d911e174863f28 ?

[andreasgou]

After 2.4.0 upgrade (from 2.2.0), I see no tasks and no Periodic task name no positional arguments. The upgrade was made in an attempt to solve a serious blocker with Oracle DB (DPI-1010 no connection) happening at random times. (I hope it is solved)

Thank you!

[auvipy]

you can try 2.3.1

[valberg]

@auvipy It works as intended in e174c9978c66f7d9c753d9332e2ec66c8abe1c1a and in fact ad508fe3433499e5fc94645412d911e174863f28 seems to be the culprit.

[auvipy]

@auvipy It works as intended in e174c99 and in fact ad508fe seems to be the culprit.

I am going to revert that

[valberg]

@auvipy I just tried setting CELERY_RESULT_EXTENDED = True and now everything is back to normal

[valberg]

I just read what ad508fe3433499e5fc94645412d911e174863f28 actually did - so my guess is that this is mostly a documentation issue?

[AmitPhulera]

Just read the conversation - You got it correct @valberg, you have to set CELERY_RESULT_EXTENDED = True in order to save additional parameters. This is the default behavior of Celery and is described here.

I was looking for places where it could be documented but did not find anything. So I ended up adding it as a minor version bump and added some info there.

[andreasgou]

Guys, you saved my day with CELERY_RESULT_EXTENDED. Now version 2.4.0 is workable!

However, PERIODIC_TASK_NAME is still empty, I'm running the task from beat.

[felixmeziere]

Same thing, I don't have the task names anymore!

[valberg]

@felixmeziere set CELERY_RESULT_EXTENDED = True and it will work as before

[licsber]

hope put this in the document, remind all new comings.

[suspiciousRaccoon]

Guys, you saved my day with CELERY_RESULT_EXTENDED. Now version 2.4.0 is workable!

However, PERIODIC_TASK_NAME is still empty, I'm running the task from beat.

Also having the same problem. Is there a fix?

[blakev]

This is still (?) broken in 2.5.1 even with CELERY_RESULT_EXTENDED = True

[Sureshlama23]

Getting blank PERIODIC_TASK_NAME & more, after setting CELERY_RESULT_EXTENDED = True. Celery 2.5.1

[oatnog]

Seems like the setting only fixes it if your broker is redis, not rabbitmq. https://github.com/celery/django-celery-results/issues/376 Are you using rabbitmq, @blakev and @Sureshlama23 ?

[blakev]

Seems like the setting only fixes it if your broker is redis, not rabbitmq. #376 Are you using rabbitmq @blakev

I'm using Redis 6/7 with Django 4.2, PostgreSQL 15/16

[Sanchows]

I had the same issue. I tried setting CELERY_RESULT_EXTENDED = True and everything is OK now. Small tip: after setting this variable just rebuild (with --build parameter) all docker containers (redis, celery worker etc.) and rerun django app.