This might be a "dumb/obvious" question but what is the difference between "task_run_version" and "flow_run_version" and which of them should represent the version I see going up at each flow register?
k
Kyle Moon-Wright
10/27/2020, 12:45 AM
Hey @wesley gabriel,
According to the context docs (which I had to refer to for your "dumb" question... 😠), both refer to the state version of instances of your flow or tasks respectively - instances of your flow/tasks are flow runs/task runs. For your latter question, the
flow_run_version
should correspond to the latest version of your flow that you've registered (the version of the current
flow_run
).
Let me know if I can clarify further!
z
Zanie
10/27/2020, 12:58 AM
To add to this a little, the
task_run_version
is bumped each time the state of the running task is changed whereas the
flow_run_version
is bumped when the flow is registered.
upvote 2
w
wesley gabriel
10/27/2020, 1:27 AM
Nice! Thank you both for the explanations. This means that I now have a problem 😅 since the version I get from the flow_run_version is stuck at 4 when it should be 13 and up... But I will investigate a bit more before asking for the expert's help
c
Chris White
10/27/2020, 2:51 AM
Hi @wesley gabriel before you go down too deep a rabbit hole, both task run and flow run versions are incremented each time the run undergoes a state change. So for flow runs, as an example, a typical version history looks like:
- 1: Pending
- 2: Scheduled
- 3: Submitted
- 4: Running
- 5: Success
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.