Skip to content

fix(consent): cap consent lookup limit at 500 (engine max) - #9

Merged
rrader26 merged 1 commit into
mainfrom
fix/consent-limit-500
Jul 2, 2026
Merged

fix(consent): cap consent lookup limit at 500 (engine max)#9
rrader26 merged 1 commit into
mainfrom
fix/consent-limit-500

Conversation

@rrader26

@rrader26 rrader26 commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

findActiveConsent listed memories with limit: 1000, but the engine rejects any limit > 500 (querystring/limit must be <= 500). So every tf.memory.consent.* operation (optOut / optIn / getStatus) hard-failed. Found while validating against QA.

Fix: use limit: 500 (the max allowed).

npm run typecheck + npm run build clean.

Note: if a subject ever has >500 memories, the client-side CONSENT filter could miss older consent records — a follow-up could query consent-typed memories directly or paginate. This PR just fixes the hard failure.

🤖 Generated with Claude Code

findActiveConsent listed memories with limit:1000, but the engine rejects
any limit > 500 (querystring/limit must be <= 500), so every consent
op (optOut/optIn/getStatus) hard-failed. Use 500, the max allowed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@rrader26
rrader26 merged commit 2c67e23 into main Jul 2, 2026
2 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.

2 participants