You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm proposing we make the following changes to the workflow management APIs in the .NET Dapr client. This is based on the feedback we got from the v1.10 alpha release of the workflow management APIs.
In StartWorkflowAsync, make instanceId and input parameters optional.
// Waits for a workflow to start running and then returns the state associated with that workflowpublic WorkflowState WaitForWorkflowStartAsync(stringinstanceId,boolfetchPayloads=false,CancellationTokencancellationToken=default);// Wait for workflow the workflow to run to completion, be terminated, or failpublic WorkflowState WaitForWorkflowCompletionAsync(stringinstanceId,boolfetchPayloads=true,CancellationTokencancellationToken=default);
As part of this work, we should also update the console app sample to use the updated Dapr client instead of workflow engine client. That will help us be confident that the new API surface area is sufficient for real use.
Describe the proposal
I'm proposing we make the following changes to the workflow management APIs in the .NET Dapr client. This is based on the feedback we got from the v1.10 alpha release of the workflow management APIs.
StartWorkflowAsync
, makeinstanceId
andinput
parameters optional.GetWorkflowResponse
withWorkflowState
from the authoring SDKWorkflowFailureDetails
property toWorkflowState
so that users can obtain more information about a workflow failure.DaprClient
:/cc @nyemade-uversky
The text was updated successfully, but these errors were encountered: