-
Notifications
You must be signed in to change notification settings - Fork 523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Demo workflow failed #901
Comments
Same issue for https://github.com/dapr/quickstarts/tree/master/workflows/csharp/sdk also.. == APP == Unhandled exception. Dapr.DaprException: Start Workflow operation failed: the Dapr endpoint indicated a failure. See InnerException for details. == APP == at Program.(String[] args) |
Hi - @Prazzy - can you confirm what OS you are running this sample? I have tried this sample on Windows, and it worked for me, so the question. Also what is the DAPR version are you running with. |
@rabollin I am using MacOS and Dapr 1.11. Yeah very strange. It did work initially but started failing after making some modifications. So it has to do with the changes I made. However, tried reverting my code changes, but still the same issue. Since other workflow code is working for me now, I am not looking into it now. So closing it for now. |
Hi, I tried to run this workflow locally, but received below error.
https://github.com/dapr/python-sdk/tree/master/examples/demo_workflow
== APP == details = "error starting workflow 'hello_world_wf': unable to start workflow: failed to start orchestration: error finding address for actor type dapr.internal.default.orderapp.workflow with id exampleInstanceID"
== APP == debug_error_string = "UNKNOWN:Error received from peer ipv4:127.0.0.1:50001 {grpc_message:"error starting workflow 'hello_world_wf': unable to start workflow: failed to start orchestration: error finding address for actor type dapr.internal.default.orderapp.workflow with id exampleInstanceID", grpc_status:13, created_time:"2023-08-30T17:19:44.361784-04:00"}"
Any help would be greatly appreciated
The text was updated successfully, but these errors were encountered: