Run Sync shows "API Error on page 1: HTTP 404 error". How do I remove an old staging site from the FeedSync Companion?

That 404 almost always means the FeedSync Companion is still connected to a site that no longer exists, usually a staging site you tested on before going live. Run Sync asks FeedSync for that old site's listings, FeedSync can't find it, and the sync stops on page 1.

You can spot it on the WordPress dashboard: Active Sites shows 2 enabled when you only have one website.

Remove the old site

  1. In WordPress, go to FeedSync › Settings › Sites. The old site shows as a long ID (like 92ddaab5-…) instead of a name.
  2. On the old site, add a value to one of its filters, such as the Agent ID (Office) Filter (anything will do, it's about to go), and press Add. This switches on the Save Settings button, which Remove Site doesn't do by itself.
  3. Press Remove Site on that site.
  4. Press Save Settings at the bottom of the page.
  5. Refresh the page: only your live site is listed, and the dashboard shows 1 enabled.

Now Run Sync works.

If the old site comes back after a refresh, it wasn't saved: do steps 2 to 4 again, and check Save Settings was pressed (it greys out again once the settings are saved).

Images not coming through?

That's a separate thing, and not your CRM. Listing details arrive in WordPress straight away; the images are added to a queue, and a cron job works through it. A staging site with no cron running never gets its images. Set up a server-side cron every 2 minutes: the steps are in Listings come through but images are slow or missing. The URL to use is also in WordPress under FeedSync › Settings › Sync › Available Endpoints › Process queued items: only that one needs a cron.