If a task run can be in a “Running” state multiple times in its lifetime, should there be an identifier that uniquely identifies a particular “run” of a task run? We could take task run ID + task_run_count to come up with an identifier for this, but I’m wondering if Prefect has thought about this or plans to support this in the future?
k
Kevin Kho
02/22/2022, 6:16 PM
You mean because of retries and retrying right? I think whatever identifier would live in the context and you are right it can be constructed with the
task_run_count
so there isn’t any more plans beyond that.What do you have in mind?
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.
