Force Sync for Yext and Uberall Listings in Sparkforge

Force Sync tells the Sparkforge listings engine to prioritize publishing your latest location data to connected directories. Use it when a routine sync is too slow or has stalled. Final timing still depends on the publisher.

When to Use Force Sync

• Faster processing for pending updates that would otherwise wait.
• On-demand escalation for urgent client changes.
• Stuck queues where one or more publishers lag behind.

Availability

Yext

• Entity level (all connected publishers).
• Publisher level (single publisher at the entity).

Uberall

• Entity level only (all connected publishers).

Prerequisites

• Active Sparkforge Listings with Yext or Uberall connected.
• An entity with valid required profile fields (business name, address, phone, hours where applicable).
• Admin role or a role with Listings write access.

Entity-Level vs Publisher-Level

Entity-Level works best after broad data changes (hours, categories, descriptions) and re-prioritizes every connected publisher for the location.

Publisher-Level (Yext only) targets a single directory when one publisher (Bing, Apple Maps, etc.) is lagging while others are current.

How to Run Force Sync

1. Go to Listings and select the entity that needs escalation.
2. Choose your scope: Entity Level or Publisher Level (Yext only).
3. Click Request Force Sync.
4. Review the confirmation and click Confirm.
5. Watch for the success notification confirming the request was queued.
6. Monitor status in Entity History or Audit Logs.

What Force Sync Cannot Do

• No guarantee of immediate publishing. Final timing depends on the publisher.
• Does not resolve policy issues like Google Business Profile suspensions, duplicates, or restricted categories.
• Does not bypass required fields. Incomplete NAP, categories, or attributes can still block publishing.
• If a sync is already running or a publisher is in maintenance, the request queues until available.

Verifying Results

Check Entity History or Audit Logs for Force Sync entries tied to the entity (and publisher, when applicable). Use timestamps to correlate the request with publisher status changes. If a publisher errors or stays unchanged for an extended period, move on to publisher-side troubleshooting.