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 Sub-Orchestration creation not working #7384

Closed
shivamkm07 opened this issue Jan 15, 2024 · 0 comments · Fixed by #7385
Closed

Workflow Sub-Orchestration creation not working #7384

shivamkm07 opened this issue Jan 15, 2024 · 0 comments · Fixed by #7385
Assignees
Labels
kind/bug Something isn't working P0
Milestone

Comments

@shivamkm07
Copy link
Contributor

In what area(s)?

/area runtime

/area operator

/area placement

/area docs

/area test-and-release

What version of Dapr?

edge: output of git describe --dirty

Expected Behavior

We should be able to create Child workflow and run it without any errors.

Actual Behavior

When trying to create and run a child workflow, workflow execution simply stalls with workflow never completing, and finally erroring out with Context deadline exceeded.

In Daprd logs, following log can be found:
iowriter.go:89: Test_Integration/daprd/workflow/workflow/daprd: time="2024-01-15T22:18:22.228973448+05:30" level=warning msg="Workflow actor '73550139-539f-443d-a5ce-bcdab2d65832': execution failed with a recoverable error and will be retried later: 'method CreateWorkflowInstance on actor '73550139-539f-443d-a5ce-bcdab2d65832:0000' returned an error: failed to unmarshal createWorkflowInstanceRequest: invalid character '\\b' looking for beginning of value'" app_id=myapp instance=MININT-0A33K9K scope=dapr.wfengine.backend.actors type=log ver=unknown

Steps to Reproduce the Problem

Try to run a workflow that creates a child workflow. It errors out as described above.

Release Note

RELEASE NOTE:

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
None yet
Development

Successfully merging a pull request may close this issue.

2 participants