Sync Engine & Troubleshooting
10 articles
- 1 How the Sync Queue Works Overview Every sync operation goes through a queue. Nothing syncs synchronously during a page request. Events are queued, then processed in background batches. This keeps your site fast and provides resilience: if a sync fails, it can be retried. The queue processor Powered by Action Scheduler (bundled). Processes every 10 seconds via WP-Cron or server... Read article
- 2 Sync Logs and Reading Them Accessing sync logs Go to Syncly > Sync Logs. [SCREENSHOT NEEDED: Sync logs table showing rows with status, type, direction, and timestamp columns] What each column means Column Description Status success: completed. failed: GHL API returned an error. pending: in queue, not yet processed. Type Kind of sync: user, contact, webhook, order, group, course, custom_object.... Read article
- 3 Enhanced Sync Logs (Pro) Overview With Pro active, each sync log entry has a View Details button. Clicking it opens a modal showing the full formatted JSON payload for that sync event. What the detail modal shows The raw request payload sent to GHL (or received from GHL). The GHL API response including status code and body. Field-level detail:... Read article
- 4 Rate Limits and API Quotas GHL API rate limits Limit type Value Burst rate 100 requests per 10 seconds per location Daily limit 200,000 requests per day What happens when limits are hit The queue processor pauses the current batch and schedules a retry. You will see “rate limit” in log entry status messages. Sync resumes automatically. Avoiding rate limit... Read article
- 5 Auto-Login Links What auto-login links do Secure one-time URLs that log a WordPress user in automatically when clicked. Useful for GHL email campaigns where you want to send users directly to a members-only page without requiring them to enter a password. How to generate one Go to Users > All Users and click on a user. In... Read article
- 6 Email Notifications Setup Overview The plugin sends automated email notifications to the admin email when certain events occur. Six notification types are available. Notification types Type When it fires connection_lost OAuth token refresh fails and the circuit breaker activates. sync_errors Sync failures exceed a configurable threshold. queue_backlog The sync queue is growing faster than it processes. rate_limit GHL... Read article
- 7 Advanced Settings (Cache, Batch Size, Retention) Overview Access from Syncly > Settings > Advanced. Cache duration Controls how long GHL contact data is cached in WordPress transients. Default: 3600 seconds (1 hour). Range: 0 (disabled) to 86400 (24 hours). Lower = fresher data, more API calls. Higher = fewer calls, potentially stale data. Batch size Queue items processed per cron run.... Read article
- 8 Common Issues and Solutions Users are not syncing to GHL Check connection status on the Dashboard. Must be green. Check WordPress Cron is running. Look at queue status in Settings > Advanced. Items queued but never processing = cron issue. Check user sync toggles in Settings > Sync Options. Field values are not appearing in GHL Go to Syncly... Read article
- 9 Frequently Asked Questions Does the plugin work with HighLevel (white-label)? Yes. The plugin connects via the GoHighLevel API regardless of branding. Configure your white-label domain in Settings > General for branded links and form embeds. Can I connect multiple WordPress sites to the same GHL account? Yes. Each WordPress site connects to a specific GHL location (sub-account). Multiple... Read article
- 10 Uninstalling the Plugin Before uninstalling Uninstalling removes all plugin settings from the WordPress database. It does not delete anything from your GoHighLevel account. It also does not delete WordPress user accounts or user meta created by the plugin. Uninstalling the Pro add-on Deactivate and delete the Pro plugin first. This does not affect the free plugin or your... Read article