Skip to content
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

Workflow status displays as Unknown after being paused using #1215

Closed
MregXN opened this issue Dec 19, 2023 · 3 comments · Fixed by #1348
Closed

Workflow status displays as Unknown after being paused using #1215

MregXN opened this issue Dec 19, 2023 · 3 comments · Fixed by #1348
Labels
kind/bug Something isn't working P0

Comments

@MregXN
Copy link
Member

MregXN commented Dec 19, 2023

Expected Behavior

workflow status should be Suspended

Actual Behavior

displays as Unknown

Steps to Reproduce the Problem

use SuspendWorkflowAsync in DaprWorkflowClient to pause a workflow instance

...
await workflowClient.SuspendWorkflowAsync(instanceId);
var getResponse = await workflowClient.GetWorkflowStateAsync(instanceId);
Console.WriteLine(Enum.GetName(typeof(WorkflowRuntimeStatus), getResponse.RuntimeStatus));
...
@WhitWaldo
Copy link
Contributor

Has any testing been done with the other language SDKs to confirm that this is an issue with the .NET SDK itself and not an issue with the sidecar implementation?

@mikeee
Copy link
Member

mikeee commented Sep 3, 2024

Has any testing been done with the other language SDKs to confirm that this is an issue with the .NET SDK itself and not an issue with the sidecar implementation?

The durabletask-go implementation and downstream dapr go-sdk is working as expected [displays the code - SUSPENDED] (although missing tests)

@cgillum
Copy link
Contributor

cgillum commented Sep 12, 2024

Looks like there's a switch case missing for Suspended in the code here. Should be an easy fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working P0
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants