Skip to main content

Troubleshooting overview

Use this section when something in Atomicat does not behave as expected. Start with the topic that best matches the symptom, then follow the checklist before contacting support.

Quick triage​

Before diving deeper, try these first:

  1. Refresh Atomicat and try again.
  2. Check your internet connection.
  3. Confirm you are signed in to the right workspace.
  4. Try a private browser window or another browser.
  5. Ask the workspace owner whether your plan or permissions changed.
  6. Capture the page URL, screenshots, and the exact time the issue happened.

Pick the right guide​

IssueStart here
You cannot access a featureAccess issues
Builder changes are not savingBuilder save issues
A page is not live or changes do not appearPublishing issues
Domain, DNS, or SSL is not workingDomain and DNS issues
Form submissions are missingForms and leads issues
Webhook delivery is failingWebhook issues
Pixels are not firing correctlyPixel issues
Funnel steps or analytics look wrongFunnel issues
Quiz flow or quiz leads look wrongQuiz issues
Video playback or embeds failVideo playback and AtomicPlayer

What to include when contacting support​

Send support:

  • Your Atomicat account email.
  • The workspace or project name.
  • The affected page, site, funnel, quiz, form, video, or product name.
  • Screenshots or a short screen recording.
  • What you expected to happen.
  • What happened instead.
  • Approximate time and timezone.
  • Browser and device.

FAQ​

When should I use this Troubleshooting overview page?

Use this page when you need to understand the workflow, settings, or decisions related to Troubleshooting overview. It is most helpful before editing a live asset, publishing changes, or troubleshooting behavior in an Atomicat workspace.

What should I check before changing Troubleshooting overview?

Confirm that you are in the correct workspace, project, page, funnel, site, or account area. Review access permissions, saved changes, publishing status, and any connected integrations before making updates.

How do I verify that Troubleshooting overview is working correctly?

Preview the affected page or feature, test the main user path in a fresh browser session, and confirm that forms, redirects, tracking, products, quizzes, or publishing states behave as expected.

What should I do if Troubleshooting overview does not work as expected?

Recheck the configuration described on this page, save the changes again, clear browser cache if needed, and test with a simple version of the setup. If the issue continues, collect the page URL, workspace details, and screenshots before contacting support.