From b2b36147ba92c277a13e3de307c37b95065227bf Mon Sep 17 00:00:00 2001 From: agumpandey Date: Tue, 12 May 2026 23:51:21 +0530 Subject: [PATCH] docs: clarify temporal enrichment async behavior --- docs/api-reference/events/get-event.mdx | 2 +- docs/openapi.json | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/api-reference/events/get-event.mdx b/docs/api-reference/events/get-event.mdx index cee5debae..c93614fc4 100644 --- a/docs/api-reference/events/get-event.mdx +++ b/docs/api-reference/events/get-event.mdx @@ -6,4 +6,4 @@ openapi: get /v1/event/{event_id}/ Retrieve details about a specific event by passing its `event_id`. This endpoint is particularly helpful for tracking the status, payload, and completion details of asynchronous memory operations. -For `POST /v3/memories/add/`, the event confirms that the write pipeline completed. If your deployment uses asynchronous temporal enrichment, the event may be `SUCCEEDED` slightly before temporal search fields become visible in subsequent `search` responses. +For `POST /v3/memories/add/`, the event confirms that the write pipeline completed. Temporal reasoning enrichment runs asynchronously by default, so the event may be `SUCCEEDED` slightly before temporal ranking signals are available to subsequent `search` calls. diff --git a/docs/openapi.json b/docs/openapi.json index 435482d57..cc7b1e0ea 100644 --- a/docs/openapi.json +++ b/docs/openapi.json @@ -419,7 +419,7 @@ }, "results": { "type": "array", - "description": "Array of results produced by the event. For add events, this confirms the write completed; temporal enrichment may continue asynchronously on some deployments." + "description": "Array of results produced by the event. For add events, this confirms the write completed; temporal reasoning enrichment runs asynchronously by default." }, "created_at": { "type": "string",