Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm going to provisionally answer my own question with a "no" -- and the hopes that someone more knowledgeable than me will come back with a solution.</p> <p>After looking more closely at the Celery documentation, I'm thinking that there simply isn't a way to access the arguments with which a parent task was called. According to the <a href="http://docs.celeryproject.org/en/latest/userguide/tasks.html#states" rel="nofollow">documentation</a>:</p> <blockquote> <p>During its lifetime a task will transition through several possible states, and each state may have arbitrary metadata attached to it. When a task moves into a new state the previous state is forgotten about..</p> </blockquote> <p>A task can be in one of the following states: Pending, Started, Success, Failure, Retry, and Revoked. For my scenario, the key here would, it seems, be the Success state. What I want to do is, for a given succeessful task, locate the id of (one of its) parent task(s), and then view the arguments with which the parent was called. However, according to the documentation, a task in the SUCCESS state will not contain this sort of data (since the parent task itself will have been successful insofar as it has spawned a child task):</p> <blockquote> <p>SUCCESS Task has been successfully executed.</p> <p>metadata: result contains the return value of the task. propagates: Yes ready: Yes</p> </blockquote> <p>In other words, it would seem that there's a hard limit here. Even if I can locate the ID of the parent task I'm interested in, because it has successfully executed, I will by definition not be able to access the arguments with which it was called because it only contains the return value (no longer its arguments).</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload