GoHighLevel snapshot troubleshooting

We have handled a few thousand snapshot installs. The support tickets cluster hard: eleven problems account for the overwhelming majority, and most are configuration rather than anything genuinely broken. Work down this list in order — it is roughly ordered by how often each one is the cause.

1. The workflows are still in draft

Imported workflows always arrive unpublished. Every single one. Open Automation → Workflows, and publish the ones on your core path first. This is the cause of maybe a third of all "nothing is happening" reports.

2. Custom values are still placeholders

If your emails mention a business that is not yours, or a price of $0, open Settings → Custom Values. Every snapshot we ship lists exactly which values need changing in its setup guide.

3. No SMS number on the sub-account

SMS steps fail silently if the sub-account has no number with SMS capability. Check Settings → Phone Numbers. A workflow that looks like it ran but sent nothing is nearly always this.

4. Email is not verified or the domain is not authenticated

LC Email needs a verified sending address; a custom Mailgun setup needs DNS records. Unverified senders bounce at the provider and never reach the contact, and GoHighLevel does not always surface the error clearly.

5. The funnel page 404s

Either the domain is not connected to the sub-account, or the funnel step path was changed after the links were written. Check Sites → Funnels → the funnel → each step's path, and compare against the buttons on the previous step.

6. The calendar shows no availability

A snapshot cannot carry your Google or Outlook connection. Reconnect the calendar, set availability, and check the timezone on both the calendar and the sub-account — a mismatch produces an empty-looking calendar rather than an error.

7. Payments fail at the order form

The payment provider connects at sub-account level, not in the snapshot. Also confirm the products exist: a snapshot brings the order form, but products with prices have to be created in Payments → Products.

8. Two workflows are fighting over the same contact

Usually caused by publishing every imported workflow at once, including a variant branch you are not running. Symptoms are duplicate emails and contradictory SMS. Unpublish the branches you do not need.

9. The trigger link or webhook points at the old sub-account

Webhook URLs and trigger links are environment-specific. Any snapshot built with an external integration will need those endpoints re-pointed after import.

10. Time-based steps are running at the wrong hour

Workflow wait steps use the sub-account timezone unless a step says otherwise. If your reminders land at 3am, the sub-account timezone is the first place to look, and the contact timezone setting on the workflow is the second.

11. It is working, and the test contact is filtered

Contacts that are marked DND, unsubscribed, or created by a previous test will not receive messages. Always test with a genuinely fresh email and phone number, and delete the test contact afterwards.

If none of those is it

Open the contact record and read the workflow history on the timeline. It shows every step the contact entered, every wait it is sitting in, and every branch it took. Nine times out of ten the answer is visible there in under a minute, and it is a faster diagnostic than re-reading the workflow builder.