From 1f923c03879f3f9da59c61569275e74607781b14 Mon Sep 17 00:00:00 2001
From: Ivan Despot <66276597+g-despot@users.noreply.github.com>
Date: Thu, 30 Jul 2026 11:06:58 +0200
Subject: [PATCH] docs: point to result.errors as the ingest failure check

The ingest() path reports failures through its return value rather than a batching context, so name result.errors as the check to use.
---
 docs/weaviate/client-libraries/python/notes-best-practices.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/weaviate/client-libraries/python/notes-best-practices.mdx b/docs/weaviate/client-libraries/python/notes-best-practices.mdx
index f3215cb4..e70a2a02 100644
--- a/docs/weaviate/client-libraries/python/notes-best-practices.mdx
+++ b/docs/weaviate/client-libraries/python/notes-best-practices.mdx
@@ -275,7 +275,7 @@ Note that these lists are reset when a batching process is initialized. So make
   language="py"
 />
 
-`collection.data.ingest()` does not use a batching context, so it reports failures through its return value instead. The `BatchObjectReturn` object that it returns exposes `result.has_errors` as a summary flag, and `result.errors` as a dictionary keyed by the position of each failed object in the input. Check `result.errors` directly, because it holds an entry for every failed object. The [one-shot ingest](#one-shot-ingest) example above shows this pattern.
+`collection.data.ingest()` does not use a batching context, so it reports failures through its return value instead. Check `result.errors`, a dictionary that holds one entry per failed object, keyed by the position of the object in the input. The [one-shot ingest](#one-shot-ingest) example above shows this pattern.
 
 ### Batch vectorization