From cb3d9e328a818bba4124a93d35fce7a86891bb39 Mon Sep 17 00:00:00 2001 From: Ori Zohar Date: Tue, 22 Dec 2020 17:07:43 -0800 Subject: [PATCH] Update daprdocs/content/en/developing-applications/building-blocks/state-management/howto-get-save-state.md Co-authored-by: Mukundan Sundararajan --- .../building-blocks/state-management/howto-get-save-state.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/state-management/howto-get-save-state.md b/daprdocs/content/en/developing-applications/building-blocks/state-management/howto-get-save-state.md index fcec20db1..2a740cad4 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/state-management/howto-get-save-state.md +++ b/daprdocs/content/en/developing-applications/building-blocks/state-management/howto-get-save-state.md @@ -42,7 +42,7 @@ The following example shows how to save two key/value pairs in a single call usi {{% codetab %}} Begin by ensuring a Dapr sidecar is running: ```bash -dapr run --app-id myapp --port 3500 run +dapr run --app-id myapp --dapr-http-port 3500 ``` {{% alert title="Note" color="info" %}} It is important to set an app-id, as the state keys are prefixed with this value. If you don't set it one is generated for you at runtime, and the next time you run the command a new one will be generated and you will no longer be able to access previously saved state.