Workflows getting stuck when using DynamoDB as an actor state store

[yevgen-el8]

Expected Behavior

DynamoDB supports workflows when enabled through actorStateStore: true

Actual Behavior

Example worklfows (both python and dotnet sdks) get stuck when using DynamoDB as an actor state store. When used with Redis, it works as expected.

Steps to Reproduce the Problem

I forked a python-sdk repo: https://github.com/evhen14/dapr-python-sdk/tree/workflow-store-issue/examples/workflow

cd examples/workflow
docker compose up -d

Observe app docker compose logs app -f to see getting stuck on Waiting for work items...
Ovserve dapr docker compose logs dapr -f to see nothing happens after logs Workflow actor 'exampleInstanceID': saving 2 keys to actor state store

The same can be reproduced with the .NET SDK

1. Use the same component from the python-sdk
2. cd to in dotnet SDK examples/Workflow/WorkflowFanOutFanIn
3. run dotnet run

Release Note

RELEASE NOTE: FIX Workflows are getting stuck when using a DynamoDB table as an actor state store.

RELEASE NOTE:

[WhitWaldo]

@mikeee Do you know if there are potentially other state store components that break when used with workflows like this? This might be worth investigating how broadly we're impacted on issues like this for 1.16.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.