Hi Manish,

This is happening because the Elasticsearch service stopped running.

As part of the first step to resolve this issue, connect to the server where the Elasticsearch is installed and restart it.

Once it is restarted, try again creating and updating the records in the Instance. This should resolve the issue.

As part of the second step to resolve this issue permanently, please debug why the service stopped running by checking the logs and apply a permanent fix to resolve it.

Hope this information helps:)

Thank you,

PK,

www.bhea.com

He Manish KUMAR,

to avoid that kind of issue, you can also configure Sugar to use a delay process so record will be synchronized with Sugar using a job instead of a live process, so no "live error" message for your customers : https://support.sugarcrm.com/Knowledge_Base/Installation_Upgrade/Installing_and_Administering_Elasticsearch/#Basic_Configuration 

$sugar_config['search_engine']['force_async_index'] = true;

Of course, it does not mean that you have to care about your elasticsearch server status and manage error. But at least, you won't scared your customers.

Fred

Thanks  Frédéric Rinaldi