Unable to sync and Cycle display Mapping sent

  • Resolved shenyin

    (@shenyin)


    3 weeks, 6 days ago

    Sync Settings:


    2024-07-10 00:41:38 Mapping sent
    2024-07-10 00:41:39 Mapping sent
    2024-07-10 00:41:40 Mapping sent
    2024-07-10 00:41:42 Mapping sent
    2024-07-10 00:41:43 Mapping sent
    2024-07-10 00:41:44 Mapping sent
    2024-07-10 00:41:46 Mapping sent
    2024-07-10 00:41:47 Mapping sent
    2024-07-10 00:41:48 Mapping sent
    2024-07-10 00:41:49 Mapping sent
    2024-07-10 00:41:51 Mapping sent
    2024-07-10 00:41:52 Mapping sent
    2024-07-10 00:41:53 Mapping sent
    2024-07-10 00:41:55 Mapping sent
    2024-07-10 00:41:56 Mapping sent
    2024-07-10 00:41:57 Mapping sent
    2024-07-10 00:41:58 Mapping sent
    2024-07-10 00:42:00 Mapping sent
    2024-07-10 00:42:01 Mapping sent
    2024-07-10 00:42:03 Mapping sent
    2024-07-10 00:42:04 Mapping sent
    2024-07-10 00:42:05 Mapping sent
    2024-07-10 00:42:06 Mapping sent
    2024-07-10 00:42:08 Mapping sent

    Status Report:

    Error	
    no such index [xxxxx-post-1]
    Recommended Solution	
    It seems the xxxx-post-1 index is missing. Delete all data and sync to fix the issue.

    The plugin cannot sync data, and it keeps displaying Mapping sent. I try to delete all data and start fresh sync, but it doesn’t work. However, I can sync normally using the command 

    wp elasticpress sync --force --setup --show-errors --yes

    The sync was successful and no errors were displayed.It seems that the plugin is repeatedly deleting the index.

Viewing 1 replies (of 1 total)
  • Plugin Contributor Felipe Elia

    (@felipeelia)

    3 weeks, 5 days ago

    The sync via dashboard works using several AJAX calls. In some setups, if things are heavily cached, WP will send the same response to ElasticPress over and over again, instead of processing what needs to be done. If you had it working using WP-CLI you should be all set now, but if you need to sync again in the future using the dashboard, I recommend you to start investigating all cache layers the website may have.

    As we don’t provide support here, if you have any follow-up questions please open an issue in our GitHub repository.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.