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
fix(strands): keep example on default extraction cadence
Use production-default extraction=True with a session-boundary flush
instead of an every-turn InvocationTrigger in the example and live tests.
Co-authored-by: Cursor <cursoragent@cursor.com>
Copy file name to clipboardExpand all lines: integrations/strands/python/CHANGELOG.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,8 +21,8 @@
21
21
22
22
- Documented that Strands' default extraction cadence is every **5 turns**, so conversation batches only reach Zep when the trigger fires (or on `flush()`), delaying graph building relative to turn-by-turn persistence — in addition to Zep's asynchronous ingestion after messages arrive.
23
23
- Documented the failure-handling contract: Zep SDK errors propagate out of `search`/`add`/`add_messages` by design, because `MemoryManager` and `ExtractionCoordinator` own failure isolation (skip-and-log, `AggregateMemoryError`, and high-water-mark rollback for retry). Added tests pinning that behavior.
24
-
- Example and live tests use every-turn extraction (`InvocationTrigger`) plus
25
-
`flush()` after `invoke_async` so demos are not flaky on the default cadence.
24
+
- Example and live tests flush at the session boundary after `invoke_async`,
25
+
which `MemoryManager` requires to persist buffered turns on that path.
0 commit comments