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

Actor TryGetStateAsync() is returning stale / previous state #1467

Open
olitomlinson opened this issue Feb 22, 2025 · 0 comments · May be fixed by #1473
Open

Actor TryGetStateAsync() is returning stale / previous state #1467

olitomlinson opened this issue Feb 22, 2025 · 0 comments · May be fixed by #1473
Assignees

Comments

@olitomlinson
Copy link

Expected Behavior

When a call is made to this.StateManager.TryGetStateAsync() then I expect the newest/current data to be retrieved.

Actual Behavior

When a call is made to this.StateManager.TryGetStateAsync() then it is retrieving a cached/previous/stale version of the state.

Image

However, if I use the Actor HTTP API to retrieve the same state key, I can see the new/current state returned as expected

Image

If I then kill the dapr/app process, and restart it, the Actor will now log out the correct state

Image

Steps to Reproduce the Problem

Release Note

RELEASE NOTE:

@olitomlinson olitomlinson added the kind/bug Something isn't working label Feb 22, 2025
@WhitWaldo WhitWaldo self-assigned this Feb 22, 2025
@WhitWaldo WhitWaldo added area/actor/client and removed kind/bug Something isn't working labels Feb 22, 2025
@WhitWaldo WhitWaldo linked a pull request Feb 22, 2025 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants