Answers.Body: <p>Algolia changed their index quotas, requiring records to be no larger than 10kb for the Community Edition plan. </p>
  
  <p>My issue was solved by upgrading my to the Essential plan, and creating a custom mapping with the Search Plus plugin, to make sure I kept the record size only as large as it needed to be.</p>
  
  <p>I was experiencing issues particularly with Commerce products that had variants and other custom fields. </p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-07T06:43:53.243Z
Answers.Text: The guys at [Top Shelf Craft](http://www.topshelfcraft.com) gave me a few pointers on how to implement a custom mapping by extending the Search Plus plugin. I've linked my solution [here](https://github.com/kojint/spcustommap).
Answers.UserDisplayName: Thabang Chukura
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-05T16:17:28.860Z
Answers.LastActivityDate: 2018-05-05T16:17:28.860Z
Answers.UserDisplayName: Thabang Chukura
Answers.Body: <p>As the first answer states, the reason why this is happening is Algolia changed the maximum record size on the free plan. When syncing the index, at some point you are likely getting a 400 error from a specific entry causing the index sync to stop.</p>
  
  <p>You can upgrade to essential to essentially get an increased record size threshold. However from the code side, you can implement a few measures to help avoid this error altogether.</p>
  
  <ul>
  <li>Truncate the returned output for fields that are typically large, so when Algolia maps it, it takes a limited value.</li>
  <li>Chunk/split larger records into parts.</li>
  </ul>
  
  <p><a href="https://discourse.algolia.com/t/spliting-long-text-to-records/3832/4" rel="nofollow noreferrer">https://discourse.algolia.com/t/spliting-long-text-to-records/3832/4</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-05T16:49:53.443Z
Answers.LastActivityDate: 2018-05-05T16:49:53.443Z
Answers.UserDisplayName: James White
Body: <p>For the past couple of months now, I've noticed on my websites using the SearchPlus plugin that indexes are no longer syncing with Algolia. This also means that creating new search indexes is not possible.</p>
  
  <p>I've been updating indexes manually via the Algolia dashboard, but this means that I can't create new indexes at all.</p>
  
  <p>My best guess is that the plugin is no longer compatible with Algolia's API. Has anyone encountered this, or come up with a fix for this issue?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-10-24T08:02:38.440Z
Comments.Text: The plugin developer is unresponsive via their website and social channels, so figuring it out is a necessity. It's a pity, because it's such a useful plugin. Using Algolia's instansearch.js is just not as easy to work with.
Comments.UserDisplayName: Thabang Chukura
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-12-27T15:11:07.353Z
Comments.Text: Any update on this?
Comments.UserDisplayName: SoHo
Tags: <search><plugin-searchplus>
Title: SearchPlus Plugin Not Syncing Indexes
ThreadText: # SearchPlus Plugin Not Syncing Indexes
  
  (Asked by: username_0 on 2017-10-24)
  
  For the past couple of months now, I've noticed on my websites using the SearchPlus plugin that indexes are no longer syncing with Algolia. This also means that creating new search indexes is not possible.
  
  I've been updating indexes manually via the Algolia dashboard, but this means that I can't create new indexes at all.
  
  My best guess is that the plugin is no longer compatible with Algolia's API. Has anyone encountered this, or come up with a fix for this issue?
  
  **Tags:** search, plugin-searchplus
  
  > **Comments:**
  > **username_0**: The plugin developer is unresponsive via their website and social channels, so figuring it out is a necessity. It's a pity, because it's such a useful plugin. Using Algolia's instansearch.js is just not as easy to work with.  
  > **username_1**: Any update on this?  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2018-05-05. Score: 1 | Accepted answer
  
  Algolia changed their index quotas, requiring records to be no larger than 10kb for the Community Edition plan.
  
  My issue was solved by upgrading my to the Essential plan, and creating a custom mapping with the Search Plus plugin, to make sure I kept the record size only as large as it needed to be.
  
  I was experiencing issues particularly with Commerce products that had variants and other custom fields.
  
  > **Comments:**
  > **username_0**: The guys at [Top Shelf Craft](http://www.topshelfcraft.com) gave me a few pointers on how to implement a custom mapping by extending the Search Plus plugin. I've linked my solution [here](https://github.com/kojint/spcustommap).  
  
  ---
  
  ### Answer by username_2 on 2018-05-05. Score: 1
  
  As the first answer states, the reason why this is happening is Algolia changed the maximum record size on the free plan. When syncing the index, at some point you are likely getting a 400 error from a specific entry causing the index sync to stop.
  
  You can upgrade to essential to essentially get an increased record size threshold. However from the code side, you can implement a few measures to help avoid this error altogether.
  
  * Truncate the returned output for fields that are typically large, so when Algolia maps it, it takes a limited value.
  * Chunk/split larger records into parts.
  
  <https://discourse.algolia.com/t/spliting-long-text-to-records/3832/4>
  
  
  ---
  
  