tinyhumansai/openhuman · error
ingest_document: ingestion failed: {e}
Error message
ingest_document: ingestion failed: {e} What it means
The rpc::ingest_rpc call into the memory driver failed after the request was built and serialized — the engine rejected or failed the ingestion. The driver's error is chained; the tool logs it before re-raising.
Source
Thrown at src/openhuman/memory/query/ingest_document.rs:127
source_ref,
};
let req = rpc::IngestRequest {
source_kind: SourceKind::Document,
source_id: source_id.clone(),
owner,
tags: vec!["agent_ingested".to_string()],
payload: serde_json::to_value(&doc).map_err(|e| {
log::debug!("[tool][memory_tree] ingest_document payload_serialize_failed err={e}");
anyhow::anyhow!("ingest_document: failed to serialize payload: {e}")
})?,
};
let outcome = rpc::ingest_rpc(&cfg, req).await.map_err(|e| {
log::debug!(
"[tool][memory_tree] ingest_document rpc_failed source_id={source_id} err={e}"
);
anyhow::anyhow!("ingest_document: ingestion failed: {e}")
})?;
let n = outcome.value.chunks_written;
log::info!(
"[tool][memory_tree] ingest_document done source_id={} chunks={}",
source_id,
n
);
Ok(ToolResult::success(format!(
"Ingested document \"{}\" as source_id={}. {} chunks created and indexed.",
title, source_id, n
)))
}
}
#[cfg(test)]
mod tests {
use super::*;View on GitHub (pinned to 7491200858)
Solutions
- Read the chained error: quota, vault, or embedder failures have distinct fixes
- Retry transient engine failures (busy store, module restart)
- Verify the memory module is healthy before re-ingesting
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at src/openhuman/memory/query/ingest_document.rs:127 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of tinyhumansai/openhuman@7491200858 (2026-08-17).
Data as JSON: /api/errors/918177553703200c.
Report an issue: GitHub.