I have identified a serious issue in Genie Agents that requires attention from the Databricks Product Team.

When a catalog is renamed, the tables that were previously configured and used within the Genie Agent disappear unexpectedly. After manually re-adding the missing tables, the issue reoccurs when the Genie Agent is cloned and additional tables are added. As a result, previously configured tables are lost again.

This issue has already occurred twice and required significant effort and time to correct, impacting productivity and maintenance of Genie Spaces.

Request to Databricks Product Team:

• Please investigate and fix this behavior so that catalog renames and Genie Space cloning operations preserve existing table configurations.
• Ensure that table references are automatically updated when catalog names change, rather than removing them from the Genie configuration.
• Consider providing a feature that allows users to easily replace an existing table with an alternative table without losing associated configurations, instructions, and metadata.
• Add validation and warning mechanisms before any operation that could result in table removal from a Genie Space.

This enhancement would significantly improve Genie Agent stability, maintainability, and overall user experience.