Merge pull request RasaHQ#11977 from RasaHQ/merge-3.4.x-main-7ae2c8d

Merge 3.4.x into main
FGA-GCES · Jan 30, 2023 · 33d724a · 33d724a
2 parents f890525 + 6ab8e30
commit 33d724a
Show file tree

Hide file tree

Showing 2 changed files with 18 additions and 0 deletions.
diff --git a/changelog/11976.doc.md b/changelog/11976.doc.md
@@ -0,0 +1 @@
+Add section in tracker store docs to document the fallback tracker store mechanism.
diff --git a/docs/docs/tracker-stores.mdx b/docs/docs/tracker-stores.mdx
@@ -394,3 +394,20 @@ extending the Rasa image to include the module, or mounting the module as volume
  a_parameter: a value
  another_parameter: another value
  ```
+
+## Fallback Tracker Store
+
+In case the primary tracker store configured in `endpoints.yml` becomes unavailable, the rasa agent will issue an
+error message and fall back on the `InMemoryTrackerStore` implementation. A new dialogue session will be started for
+each turn, which will be saved separately in the `InMemoryTrackerStore` fallback.
+
+As soon as the primary tracker store comes back up, it will replace the fallback tracker store and save the
+conversation from this point going forward. However, note that any previous states saved in the `InMemoryTrackerStore`
+fallback will be lost.
+
+:::warning Using the same redis instance as lock-store and tracker store
+
+You must not use the same Redis instance as both lock store and tracker store.
+If the Redis instance becomes unavailable, the conversation will hang because there is no fall back mechanism
+implemented for the lock store (as it is for the tracker store interfaces).
+:::