Skip to content

Fix: Pass knowledge_card_id to crew to prevent UUID error

Edouard Legoupil requested to merge fix-knowledge-crew-uuid-error into main_dev

Created by: Edouard-Legoupil

The ContentGenerationCrew was incorrectly using a string from the task description as the knowledge_card_id for a vector search, causing a database error due to an invalid UUID format.

This was resolved by refactoring the ContentGenerationCrew and its VectorSearchTool to accept the knowledge_card_id during initialization.

The API layer was updated to pass the card_id when creating the crew, ensuring the correct UUID is used and preventing the agent from having to infer the ID from the prompt.

  • Does my code meet the quality standards for releasing packages?
  • Does the reviewer have all the information to validate the features/issues without too much research?
  • Does the customer who will validate the associated tickets have the information to do so without wasting time?

Issues to validate to close :

  • issue #

Processed issues to keep open or in progress:

  • issue #

Checklist:

  • Does the package check go local?
  • Does the CI pass?
  • Are the added / fixed features documented, tested?
  • Are the added features / solved problems briefly presented in the PR message?
  • Are the changes related to tickets / issues that I have listed in the commits and in the PR itself?
  • Are the tickets in "review" mode in the Project Tracking Board?
  • Does each ticket, if it is to be closed after acceptance of the PR, contain a comment that tells how to validate it?

Merge request reports