SubOrchestrator is not completing the execution.

[aminch18]

Dear team,

I implemented an Orchestration in order to migrate some data, probably Durable Functions are not the best approach but always works for me. Today, I had a problem that my SubOrchestrator is not raising the ExecutionCompleted event. I really don't know what is happening.

I purged the all instances history, but is like the SubOrchestrator began in a loop and never finish it.

This is the Sequence Diagram now, I would like to know if you could know anything that could help me with this situation.

If this SubOrchestrator never raise the event of ExecutionCompleted it'll never be completed this instance, and I would like to know what is happening.

The final sequence diagram should be like this:

I did not change anything about code, it is the same and always worked, but today began to do this loop and I really don't know what is happening.

Could you help me with this?

[cgillum]

For help with debugging these kinds of issues, it's best if you can share some additional information, such as where your code is running (local? Azure?), the language you're using, what is the instance ID of the impacted orchestration, and whether the logs contain any relevant information. Can you share more information about the sub-orchestration which isn't completing?

[aminch18]

Dear @cgillum,

I am using C# and .NETCore 3.1, Azure Function Version as v3, and the functions were deployed in Azure with Elastic Premium EP1 using 4 instances.

In logs, I saw that no exception have been thrown, and in fact the MigrateUserAlertActivity is storing correctly the data in Cosmos DB, but doesn't finish. And for this reason is not doing the next iteration this is the code of SubOrchestrator:

Orchestrator code:

SubOrchestrator code:

Thanks in advance 😊

[aminch18]

Dear @cgillum, this is still happening even though I updated Durable Functions extensions. I created a new host, but it is still not raising the events internally, and the sub orchestrator is not doing the loop properly.

[cgillum]

Thanks for checking, @aminch18. Do you have another orchestration instance ID that I can look at from after you upgraded the extension version?

[RDavis3000]

@aminch18 What happened next? I'm experiencing a similar problem!

[aminch18]

@RDavis3000, I've resolved this basically deleting my Azure Function and recreate it, I could not find the root cause, it seems that some data was corrupted inside the AZ Storage related to the AZ Function.

[aminch18]

@cgillum Thanks for all your help.