Return correct UUID for failed objects

Open
#942 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@rayensamali is already working on this.

Since Mar 6, 2026.

  • #1978 by @rayensamali — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start by tracing the failed_objects handling shown in the issue and find where original_uuid is assigned or lost. Confirm the cases where it is None, then ensure failed UUID collection and logging use the correct object UUID; add or run the relevant failure-path tests if they exist.

Written by the indexing model from the issue text.

Description

bug
    for failed_object in failed_objects:
        failed_uuids.add(failed_object.original_uuid)
        LOGGER.error(f'Unexpected exception {failed_object.message} creating weaviate object {failed_object.original_uuid}')

This original_uuid seems to be none in some cases

Dominant language
Python
Stars
230
Forks
173
Avg merge
4d 16h
Merged PRs (30d)
23

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from weaviate/weaviate-python-client

All issues in weaviate/weaviate-python-client

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.