what is execution_id? when getting a workflow instance from databases, we select record by instance_id and execution_id as filters, why execution id is necessary? Is instance id not unique enough ? #189
|
I read the source code and think that execution_id is the same life cycle as the instance id that doesn't change at all, so I don't understand why the execution_id is necessary. |
Answered by
cschleiden
Apr 20, 2023
Replies: 1 comment 1 reply
|
You are right, currently it's not used at all. This relates to the Durable Task concept of "Eternal orchestrations": https://learn.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-eternal-orchestrations?tabs=csharp I thought of integrating this in go-workflows, too, but for now decided against it. It could be removed I just haven't gotten to it yet. |
1 reply
Answer selected by
abserari
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
You are right, currently it's not used at all. This relates to the Durable Task concept of "Eternal orchestrations": https://learn.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-eternal-orchestrations?tabs=csharp
I thought of integrating this in go-workflows, too, but for now decided against it. It could be removed I just haven't gotten to it yet.