mode
mode="long-range" is the default, so you can leave it out. fast is accepted too, but both run the same extraction pipeline today (entity resolution, preference detection, relationship mapping), so the choice does not change what a backfill extracts. See Ingestion mode.
Why document_created_at
Synap uses document_created_at as the ground-truth timestamp for temporal reasoning, recency ranking, and aging. Don’t skip it: without it, every memory looks like it happened today, and recency-weighted retrieval breaks. Pass the original timestamp from your database.
Why batch and not one-by-one
batch_create accepts up to 100 documents per call, and the cloud queues them on a backfill-friendly path that doesn’t slow real-time ingestion. One-by-one would 30x your wall-clock time and burn rate limits.
Idempotency
If you re-run the backfill (because you found a bug, or because you’re bringing online a second region), pass a stable document_id derived from your DB row:
document_id; duplicates surface as per-document failures in the batch_create response (results[].status / results[].error_message). Inspect the response and skip rows that already exist:
mode. Talk to support if you have multi-million-turn backfills and want a higher throughput allocation for the window.
Going further
- Guides: Migrating from Mem0 / Zep / Letta
- Cookbook: AI SDR · Salesforce: Enterprise Sales Assistant
- Patterns: Graceful Degradation