@mramanindia 

The underlying issue here is likely the workspace cross Geo data processing requirement. In Databricks, content search on managed volumes relies on background Vector Search indexing infrastructure that is not deployed in every single cloud region. For eu-west-2 (London) along with Frankfurt, Ireland, Paris, Central Canada, São Paulo, Tokyo, Seoul, Singapore, Jakarta and Mumbai - Databricks handles the document indexing workload in a secondary geography. When a workspace restricts processing to its local boundary, the service rejects the indexing request and surfaces that generic Failed to update content search - The request was invalid error in Catalog Explorer.

Content search is fully supported on Default Storage and serverless workspaces. Managed volumes residing on Default Storage work without issue for volume content search, so the storage architecture is not the limiting factor. There is currently no public API or workspace-level log stream that exposes more granular validation errors for this error. The action triggers backend infrastructure provisioning within Databricks-managed control planes, which throws the downstream geo-restriction errors before reaching the UI or workspace APIs.

To resolve this, an account administrator needs to permit cross-region processing for Designated Services on the workspace

• Open the Databricks Account Console
• Navigate to Workspaces in the sidebar and select your London workspace.
• Open the Security and compliance tab.
• Disable Enforce data processing within workspace Geography for Designated Services.

Toggling this off grants Databricks permission to run the required document parsing and vector indexing pipelines outside eu-west-2. Once updated at the account level, re-enabling content search on your managed volume should complete successfully, allowing the Genie Agent to retrieve content from the PDFs for hybrid queries. More details here