Potentially dumb Q - is there a way to not update ...
# ask-community
z
Potentially dumb Q - is there a way to not update the flow version when doing a
flow.register()
? So that if multiple identical tasks (either autodetect through hashing the flow object (?) or using a client provided ID) are submitted through different agents all of the agents can run the same flow
c
Hi @Ziyao Wei - unfortunately not at this time; the main reason is that the task IDs which are put in the database are derived from their IDs as python objects, so every time you recreate the Flow you need to re-register it
z
Cool, thanks! That makes sense, but it’ll be great to be able to configure this so we can use, e.g.,
git rev-parse HEAD
Also - is the task ID not a deterministic hash? Is it something like hash(obj + timestamp)?
c
I’ll have to remind myself exactly the implementation but unfortunately it is non-deterministic