Open justinmchase opened 1 year ago
The orchestration function itself seems to be running fine:
Executing 'Functions.HelloExample' (Reason='(null)', Id=c282b3cd-430a-401d-8f32-054076109771)
I "Hello Workflow Running: (null) (17c9b0b5037c4b9e81730d626715a0a1)" {"category":"Recovery.Functions.HelloExample"}
Hello Workflow Running: (null) (17c9b0b5037c4b9e81730d626715a0a1)
Executed 'Functions.HelloExample' (Succeeded, Id=c282b3cd-430a-401d-8f32-054076109771, Duration=1ms)
17c9b0b5037c4b9e81730d626715a0a1: Function 'HelloExample (Orchestrator)' completed. ContinuedAsNew: False. IsReplay: False. Output: (36 bytes). State: Completed. HubName: TestHubName. AppName: . SlotName: . ExtensionVersion: 2.9.0. SequenceNumber: 118. TaskEventId: -1
Hi. Same issue as @justinmchase here. It happens to me even when creating a new Durable Function using the template from VS:
Any update on it, please?
I can't remember for sure but I think it was adding the AzureWebJobsSecretStorageType
to the local.settings.json
file that solved it for me.
{
"IsEncrypted": false,
"Values": {
"AzureWebJobsStorage": "<redacted>",
"FUNCTIONS_WORKER_RUNTIME": "dotnet-isolated",
"AzureWebJobsSecretStorageType": "files"
},
}
Mmm, thanks for that @justinmchase, but no luck, that didn't make the trick for me. Same error.
But actually you pointed to the right direction @justinmchase , it was an storage issue. For some reason it's not working for me when running locally using Azurite (even when Azurite is working ok for other APIs). I just shut down my Azurite container and run the storage emulator instead and started to work. It's a pain, as using Azurite with Docker is much easier, actually I think Storage Emulator is deprecated? But it works now anyway.
Thanks!
Check the version, now that you say it I recall having to update the azurite version I was using also.
Same here. Have tried to upgrade azurite
and the AzureWebJobsSecretStorageType
- didn't help
I have same issue , how to ?
i have resolved the issue need register on program.cs
services.AddDurableTaskClient(builder =>
{
// Configure options for this builder. Can be omitted if no options customization is needed.
builder.Configure(opt => { });
builder.UseGrpc(); // multiple overloads available for providing gRPC information
// AddDurableTaskClient allows for multiple named clients by passing in a name as the first argument.
// When using a non-default named client, you will need to make this call below to have the
// DurableTaskClient added directly to the DI container. Otherwise IDurableTaskClientProvider must be used
// to retrieve DurableTaskClients by name from the DI container. In this case, we are using the default
// name, so the line below is NOT required as it was already called for us.
builder.RegisterDirectly();
});
It seems like we soon will celebrate a one year anniversary of this issue. None of the above solutions help me. Still getting this stupid error with no details whatsoever. If I switch to .NET 6 - everything works fine.
same error, in local it's working fine but in when deploying to docker where my azurite is running getting grpc error when creating durable function
I have two functions, one is a CronTrigger, which appears to be working fine the other is an OrchestrationTrigger function. This is running in
dotnet-isolated
, net7, in docker.I can see in my logs that the cron is launching, it also successfully schedules the other function, i can see the instanceId in the logs.
The line where I call
WaitForInstanceCompletionAsync(instanceId, ...)
is where it throws an exception. Here are the details:I'm not sure how this can happen. This is running in a pod, which has both processes...
Example code
Full error and stack