Consistently seeing "Error Occurred during query execution" in multiple 10x instances
I am seeing this error pop up in several places in 10x instances. These are both demo instances and customer instances. I have seen them inside of home pages, when trying to render charts, and in things like lead pages.
Anyone else come across this? Is this small bug with patch coming? At first I thought was maybe something in a chart configuration it didnt like, but now seeing it in lead pages tells me something more in back end.
Like
I've not noticed that, at least not yet - although not really paid attention to any dashboards/charts/etc. If you look at the network requests in dev tools, do you see any requests in red (likely a SelectQuery) that might shed some light on what is causing the error?
Support dug into it... issue with Global Search. If anyone sees this error... here is what you can do
Keep in mind noone has seen this in prod yet because very few instances are on 10x... This will only apply to your lower environments where globalsearch is not enabled.
This setting connects your Creatio instance to the Global Search service (powered by Elasticsearch), enabling high-speed, cross-functional search across the entire platform.
When this setting is empty, but the search features are active, the system attempts to initialize a connection to a non-existent service, resulting in the "Error occurred during the query execution" message you've seen.
Workaround for Development/Demo Environments
If you do not require Global Search functionality in your development or demo instances, you can resolve the error by fully disabling the feature. Simply clearing the URL is often insufficient as the application will still attempt to call the service.
To fully disable it, please follow these steps:
1. Disable Feature Flags: Navigate to the Feature Selection page ([YourSiteURL]/0/Shell/#Section/Feature_ListPage) and turn OFF the following flags:
GlobalSearch
GlobalSearch_V2
GlobalSearchRelatedEntityIndexing
2. Clear System Settings: Ensure the following settings in the System Settings section are empty:
GlobalSearchUrl
GlobalSearchConfigServiceURL
GlobalSearchIndexingApiUrl
3. Restart & Cache: After saving these changes, please restart the application pool and clear the Redis cache to ensure the changes take effect.
This will stop the system from attempting to use the Global Search service and resolve the query execution errors.