JDSS/mem0
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(profiles): correct response example and regenerate cadence from live API

Browse Source 
Live e2e against the feature neuron: the profile envelope has no generation_count, and the regenerate cooldown is once per day (86400s), not hourly.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
karthik
2026-09-15 21:46:53 +05:30
co-authored by Claude Opus 4.8
parent ac2c5cbfbf
commit b852f9240c
1 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/platform/features/user-profiles.mdx
+3 -4
View File
@@ -137,8 +137,7 @@ A response looks like this:
"status": "succeeded", "status": "succeeded",
"entity_type": "user", "entity_type": "user",
"entity_id": "alice", "entity_id": "alice",
"updated_at": "2026-02-08T10:30:00Z", "updated_at": "2026-02-08T10:30:00Z"
"generation_count": 4
} }
``` ```
@@ -221,7 +220,7 @@ await client.regenerateProfiles();
``` ```
</CodeGroup> </CodeGroup>
This returns immediately and runs in the background; a large project takes a while. It is limited to one run per project per hour, so sample first and regenerate once you are satisfied. This returns immediately and runs in the background; a large project takes a while. It is limited to one run per project per day, so sample first and regenerate once you are satisfied.
## When profiles update ## When profiles update
@@ -306,7 +305,7 @@ Generation is asynchronous and needs enough to work with. Branch on `status`: `p
No. `sample_profiles` runs real generations against real memories and **keeps** the profiles it produces, so it counts toward your usage like any other generation. It exists to check a schema on a few entities before you commit to it — not as a zero-cost dry run. No. `sample_profiles` runs real generations against real memories and **keeps** the profiles it produces, so it counts toward your usage like any other generation. It exists to check a schema on a few entities before you commit to it — not as a zero-cost dry run.
**Does changing the schema rewrite existing profiles?** **Does changing the schema rewrite existing profiles?**
No. A schema change applies to future generations. To apply a new schema to entities that already have a profile, call `regenerate_profiles` (rate-limited to once per project per hour). No. A schema change applies to future generations. To apply a new schema to entities that already have a profile, call `regenerate_profiles` (rate-limited to once per project per day).
**What happens to a field I remove from the schema?** **What happens to a field I remove from the schema?**
It stops being maintained. On an entity's next generation, fields your schema no longer defines are pruned from the stored profile — so keep a field in the schema for as long as you want its value kept. It stops being maintained. On an entity's next generation, fields your schema no longer defines are pruned from the stored profile — so keep a field in the schema for as long as you want its value kept.