## 📋 Overview

When you schedule a social or GBP post in Search Atlas, it is queued for publication and then synced to your connected GoHighLevel (GHL) account. This sync does not happen instantly — there is a processing window you should expect before the post appears inside GHL.



## ⏱️ How Long Does Syncing Take?

Under normal conditions, a scheduled post created in Search Atlas will appear in GoHighLevel **within a few minutes up to 1 hour** after the scheduled publish time. The exact timing depends on:

- **Queue load:** High-volume publishing periods may add a short delay to processing.
- **GHL API response times:** Occasionally, GoHighLevel's API takes longer to acknowledge and reflect the incoming data on their end.
- **Post type and account configuration:** Some post types or sub-account setups in GHL may surface synced content in different sections of the platform.

If your post has not appeared in GHL within **2 hours** of its scheduled time, this is outside the expected window and warrants further investigation.



## 📍 Where to Create and Schedule Posts in Search Atlas

Posts are managed from **Left sidebar → Local → Posts**. From this screen you can create new posts, set a publish date and time, and connect your GHL integration before scheduling.



## 🔍 What to Check Before Contacting Support

Before escalating, run through the checklist below — most delayed-sync issues are resolved at one of these steps:

1. **Confirm the post status in Search Atlas:** Go to **Left sidebar → Local → Posts** and verify the post shows a status of **Scheduled** or **Published**, not **Draft** or **Failed**.
2. **Check the scheduled time and timezone:** Make sure the publish time was set in the correct timezone. A mismatch between your Search Atlas account timezone and your GHL sub-account timezone is a common cause of apparent delays.
3. **Verify the GHL integration is active:** Confirm your GoHighLevel account is still connected and authorised. If the OAuth token has expired, posts will queue but not deliver. Reconnecting the integration and re-saving the post typically resolves this.
4. **Look in the correct GHL location:** Synced posts may appear under the **Social Planner** section of your GHL sub-account. If you are looking elsewhere in GHL, the post may already be there.
5. **Wait the full 2-hour window:** If the scheduled time was recent, allow the full 2 hours before treating it as a failed sync.

## ⚠️ Common Reasons a Post May Not Appear in GHL

- The GoHighLevel integration was disconnected or the access token expired after the post was scheduled.
- The post was saved as a **Draft** instead of being fully scheduled.
- A timezone mismatch caused the post to be queued for a future time that has not yet been reached.
- The GHL sub-account selected at the time of scheduling no longer matches the currently active integration.
- A temporary GHL API outage delayed the handoff; these usually self-resolve within a few hours.

## 🔄 How to Resync or Reschedule a Post

1. Go to **Left sidebar → Local → Posts**.
2. Locate the affected post and open it for editing.
3. Verify all settings — GHL account, scheduled time, and timezone — are correct.
4. If the post status shows **Failed**, update the scheduled time to a near-future time and save it again to re-queue it for delivery.
5. Monitor the post status; it should update to **Published** once GHL confirms receipt.

## 💬 Need More Help?

If you have followed all the steps above and your post still has not synced to GoHighLevel after 2 hours, our team can investigate the delivery logs directly. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.