Skip to content

fix: use memoryStrategyId instead of strategyId in search_long_term_memories#314

Merged
tejaskash merged 1 commit into
mainfrom
worktree-fix-issue-303
Mar 11, 2026
Merged

fix: use memoryStrategyId instead of strategyId in search_long_term_memories#314
tejaskash merged 1 commit into
mainfrom
worktree-fix-issue-303

Conversation

@tejaskash

@tejaskash tejaskash commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Fixes MemorySessionManager.search_long_term_memories sending strategyId instead of memoryStrategyId in the search criteria passed to the boto3 retrieve_memory_records API, which requires memoryStrategyId.
  • Updates corresponding test assertions to match the corrected parameter name.

Closes #303

Test plan

  • Existing unit tests updated and passing (294 tests in memory suite)
  • test_search_long_term_memories_with_strategy verifies memoryStrategyId is sent
  • test_search_long_term_memories_without_strategy_id verifies key is absent when not provided

…emories

The boto3 retrieve_memory_records API requires memoryStrategyId in
searchCriteria, but MemorySessionManager was sending strategyId,
causing a parameter validation error.

Fixes #303

@jariy17 jariy17 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tejaskash tejaskash merged commit a30f8da into main Mar 11, 2026
22 of 23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MemorySessionManager sending strategyId instead of memoryStrategyId in method search_long_term_memories to internal boto3 client and failing

3 participants