# Resync a table to a dataset

Datasets can be synced to Lime (ElasticSearch) so that full-text search, aggregations, and edits can be performed with applications like Fusion. Sometimes it is necessary to re-sync datasets, such as when the underlying Elasticsearch cluster needs to be migrated. It can also be required if the existing index is under-provisioned for the size of data.

Generally, re-syncs either happen on a schedule, or are automatically triggered by the platform. Occasionally, automatically triggered re-syncs may fail, in which case they need to be triggered manually and any errors must be resolved.

## How to trigger a re-sync

Follow the steps below to trigger a resync for a dataset (all data shown in example images is notional):

1. Select the dataset to open its preview.

2. Navigate to the **Details** tab.

   <br /><img src="../../../assets/a105d5989e80f425de400001972f96a60fbb01f78ea17b2936c08cbf0332217b.webp" style="max-width: 424.5px;" />

3. Select **Sync Status**.

   <br /><img src="../../../assets/ab5a70d97a984cdd52bceda7e1456d0cd209cd5559875ac695083a3936e9a9bf.webp" style="max-width: 424.5px;" />

4. If a sync is currently running, wait for it to complete before proceeding.

5. Select the small triangle next to **Sync to Lime (ElasticSearch)** to expand the details for the Object Store V1 (Phonograph) sync.

   <br /><img src="../../../assets/f46d4cd6a7b6b508d8b4889178a04b7ac9c41bcffd218f69db666a89ccadf610.webp" style="max-width: 424.5px;" />

6. Select the blue **Sync** button that appears.

   <br /><img src="../../../assets/120f31ce4198df9595b47484d339989784e40a1c1f1ece3ac8a4d3e1525f0cb1.webp" style="max-width: 424.5px;" />

## Frequently asked questions

* What should I do if the re-sync fails?

  Consult the job details to investigate the cause of the reindex job failure. The job details page should explain the failure reason and suggest resolution steps.