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
Dapr workflow should complete without error when the actor state store is DynamoDB.
If the value which is saved in DynamoDB state store is any binary data, save it as DynamoDB binary data type.
Actual Behavior
The following error occurs when the workflow quickstart code runs.
2025/01/10 00:05:00 failed to start workflow: failed to start orchestrator: rpc error: code = Unknown desc = error from internal actor: InternalFailure: The request processing has failed because of an unknown error, exception or failure.
== APP - order-processor == status code: 500, request id: 263b9cb8-2ddd-4ef1-9bcc-402853c8319c
== APP - order-processor == exit status 1
The App process exited with error code: exit status 1
This is because DynamoDB state store doesn't fully support binary data value.
When a state is saved in DynamoDB state store, the value is converted to string. If the string contains invalid UTF-8 sequences, DynamoDB throws error.
Steps to Reproduce the Problem
Create DynamoDB table with primary key (attribute name: key)
Expected Behavior
Dapr workflow should complete without error when the actor state store is DynamoDB.
If the value which is saved in DynamoDB state store is any binary data, save it as DynamoDB binary data type.
Actual Behavior
The following error occurs when the workflow quickstart code runs.
This is because DynamoDB state store doesn't fully support binary data value.
When a state is saved in DynamoDB state store, the value is converted to string. If the string contains invalid UTF-8 sequences, DynamoDB throws error.
Steps to Reproduce the Problem
Release Note
RELEASE NOTE:
The text was updated successfully, but these errors were encountered: