Troubleshooting

🛠️ Troubleshoot Non-Clickable Loop Artifacts

🔍 What this issue means Some loop runs produce output artifacts that appear in Search Atlas but cannot be opened or clicked. This usually means the output is still loading, was not saved as an interactive artifact, or the page displayed an outdated session state. ✅ Check the loop output 1. Open the loop and wait for the run to finish completely. 2. Check whether the output is labeled as an artifact, result, or plain text. Only interactive artifacts include an openable destination. 3. Refresh the page once the run is complete. A refresh can restore the artifact when the first page load shows incomplete output data. 4. Open the loop again and check whether the artifact is now clickable. 🧭 Understand expected behavior Not every loop output is designed to open as a separate artifact. Text, status messages, evaluation results, and other informational output may be displayed without a link. Interactive outputs should provide a clickable target when the artifact has been successfully created and saved. ⚙️ If the artifact remains unavailable - Confirm that the loop run completed without an error. - Try refreshing the page and reopening the relevant workspace or issue. - Check whether the output appears consistently across repeated runs. - Record the loop name, run time, output type, and the URL of the affected page. - Take a screenshot showing the non-clickable output, if possible. Do not repeatedly regenerate the loop if the output is missing. Re-running may create a different result and make the original issue harder to investigate. 💬 Contact support If the output should be interactive but remains non-clickable after these steps, share the recorded details with our team so we can investigate the specific run. 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.

🚀 Fix a Stuck Quest LLM Digital PR Campaign

🔍 Overview The Quest AI Visibility (formerly LLM Visibility) tool inside the Authority module lets you run AI-powered Digital PR campaigns that pitch your content to language models. If your campaign is stuck on Paused — even after a support team member has said the issue was resolved — this article walks you through the most common causes and the steps to fix them. 📍 How to Find Your Campaign 1. Open Search Atlas and click Authority in the left sidebar. 2. Select QUEST AI Visibility (formerly LLM Visibility) from the sub-menu. 3. Locate your campaign in the table. Check the status column for Paused. ⚠️ Common Reasons a Campaign Gets Stuck on Paused - Credit balance dropped below the required threshold — even briefly. The system pauses a campaign the moment credits fall short and does not always auto-resume when credits are topped up. - No active contacts selected — a campaign needs at least one valid contact assigned before it can run. - Campaign saved in draft state — if the setup wizard was closed before the final confirmation step, the campaign remains paused. - A recent platform update reset campaign states — UI and styling migrations can occasionally affect campaign status flags. Our engineering team actively monitors and resolves these cases. - Contact list issues — invalid, duplicate, or unverified contacts can prevent delivery and trigger an automatic pause. 🛠️ Step-by-Step Troubleshooting 1. Check your credit balance. Go to the top-right avatar → Billing (Plans & Top-ups) and confirm you have enough credits for the campaign scope. If your balance is sufficient but the campaign is still paused, continue to the next step. 2. Manually resume the campaign. In Authority → PR Distribution (Press Releases), find your release row and click the Resume link/button directly in that row. If the row is not visible, try refreshing the page — a recent fix addressed missing column headers in this table. 3. Verify your contact selection. Open the campaign and review the contacts assigned to it. Make sure at least one contact is active and verified. Remove any contacts marked as invalid or bounced. 4. Re-save the campaign. Open the campaign editor, review each step of the setup wizard, and click Save or Confirm on the final step. This forces the system to re-evaluate the campaign state. 5. Check the Campaigns sub-page. Navigate to Authority → Campaigns for a full list of all campaign statuses. Compare the status here with what you see in QUEST AI Visibility (formerly LLM Visibility) to rule out a display discrepancy. 6. Review Sent and Inbox logs. Go to Authority → Sent and Authority → Inbox to confirm whether any outreach was delivered before the pause. This helps identify exactly when the campaign stopped. 👥 How to Review and Update Contact Selection Correct contact selection is critical for a Digital PR campaign to run successfully. Follow these steps to audit your contacts: 1. Open your campaign from Authority → QUEST AI Visibility (formerly LLM Visibility). 2. Navigate to the Contacts or Sources step inside the campaign editor. 3. Confirm that all listed contacts have a verified status. Remove or replace any that are flagged as invalid. 4. Add new contacts if the list is empty. Use relevant, niche-specific contacts to maximise campaign reach. 5. Save your changes and attempt to resume the campaign. ✅ What to Do If the Campaign Is Still Paused If you have followed all the steps above and the campaign remains stuck on Paused, the issue may require a backend investigation by our team. This can happen after platform updates that affect campaign state flags — our engineering team resolves these on a case-by-case basis. 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. When you reach out, have the following ready to speed up the investigation: - Campaign name and the date it was last active - A screenshot of the current status in QUEST AI Visibility (formerly LLM Visibility) and in Campaigns - Your current credit balance - Any error messages displayed in the Actions menu or campaign editor

🔧 Fixing the "Query Failed - Creating Query Failed" Error in QUEST AI Visibility

If you use QUEST AI Visibility (formerly LLM Visibility) to track how your brand appears across AI assistants, you may occasionally see a "Query Failed - Creating query failed" error when adding or running a query. This message means the query could not be created or processed. In most cases, the cause is straightforward and can be fixed in a few minutes. This article explains why the error happens and walks you through the steps to resolve it. 🤔 Why This Error Happens The "Creating query failed" error usually appears for one of these reasons: - Formatting issues in the query text, such as unsupported characters, emojis, or extra line breaks. - A query that is too long or too short, falling outside the accepted character range. - Duplicate queries that already exist under the same topic in your project. - Plan or quota limits have been reached for the number of queries allowed. - The project or workspace is not fully set up (for example, a missing brand name, domain, or region). - The analysis timed out — very broad or complex queries can take a long time to process, and the request to the AI provider may time out and return a failure after an extended "analyzing" period. - A temporary connection issue between QUEST and the AI provider. 🛠️ How to Fix It Work through the steps below in order. Most customers resolve the issue within the first three steps. 🔄 Step 1: Refresh and Try Again 1. Refresh your browser page. 2. Re-enter the query and click Create or Run again. Many failures are caused by a brief, temporary connection issue, and a simple retry often resolves it. However, if a query keeps failing, avoid submitting it many times in a row: each failed attempt can use a query credit, and repeatedly retrying the same failing query can create duplicate entries. If one or two retries don't work, move on to the steps below or contact support rather than retrying repeatedly. ✍️ Step 2: Check Your Query Text 1. Remove any emojis, special symbols, or unusual punctuation. 2. Delete extra spaces and line breaks so the query is a single, clean sentence. 3. Make sure the query is a clear, natural-language question or phrase (for example, "What are the best project management tools?"). 4. Confirm the query is not too short (a single word) or excessively long, as queries that exceed the accepted length are a known rejection reason. 🔍 Step 3: Look for Duplicates 1. Open your list of existing queries in the project. 2. Confirm the query you are trying to add does not already exist under the same topic. 3. If it does, edit the existing query instead of creating a new one. ⚙️ Step 4: Confirm Your Project Setup 1. Open your QUEST AI Visibility (formerly LLM Visibility) project settings. 2. Make sure required fields are complete in Create Project (Settings → Use the new project setup experience), including Website domain, Market Location, and Language. 3. Save any changes, then try creating the query again. 📊 Step 5: Review Your Plan Limits 1. Check how many queries you have used against your plan's allowance. 2. If you have reached your limit, remove unused queries or upgrade your plan. 3. If a series of failed attempts seems to have reduced your available queries faster than expected, note this and contact support (see below) so we can review your account. 📨 If the Error Continues If you have completed all the steps above and the error still appears, please contact our support team so we can investigate further. To help us resolve your issue quickly, include the following details: - The exact query text you are trying to create. - The name of the project or workspace where the error occurs. - A screenshot of the error message. - The date and approximate time the error appeared. - The browser you are using. You can reach us through the in-app chat or by emailing our support team. Providing the information above allows us to reproduce the issue and respond faster. If repeated failed attempts have reduced your available queries, let our team know — we can review your account and restore query credits that were consumed by failed attempts. 💡 Tips to Prevent Future Failures - Keep queries clear, concise, and written in plain language. - Avoid copying text directly from formatted documents, which can carry hidden characters. - Keep queries focused rather than overly broad, since very large or complex queries are more likely to time out during analysis. - Periodically review and clean up unused queries to stay within your plan limits. - Complete all project setup fields before adding queries. Following these practices helps ensure your QUEST AI Visibility (formerly LLM Visibility) queries run successfully every time.

🐛 Fix: Co-worker Scheduled Jobs Now Manageable

A bug that blocked users from deactivating or deleting co-worker scheduled jobs has been fixed, restoring full control over scheduled job management. ✨ What's New Previously, co-worker scheduled jobs could not be deactivated or deleted, leaving users unable to manage or clean up automation tasks assigned to co-workers. This issue has been resolved — all scheduled jobs, including those associated with co-workers, can now be fully managed as expected. 🛠️ How to Use It 1. Navigate to the scheduled jobs section within your workspace. 2. Locate the co-worker scheduled job you wish to manage. 3. Use the available options to deactivate or delete the job as needed. 📋 What to Expect Deactivating a scheduled job will pause it without permanently removing it, while deleting it will remove it entirely. This fix applies to all co-worker scheduled jobs across your account. No additional configuration is required — the controls are available immediately. 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.

🔧 Fix LLM Tool and Topic Monitoring Access Issues

🧭 Overview If you cannot add topics to monitor AI search performance or the Search Atlas LLM tool appears locked or non-functional, the cause is almost always one of four things: your subscription tier does not include the feature, the feature has not been enabled on your account, your user role lacks the required permissions, or a setup step was missed during onboarding. This article walks you through each scenario so you can identify and fix the issue quickly. 📋 Before You Begin Gather the following information before running through the steps below. This will save time if you need to escalate: - Your current plan name and monthly cost - The email address on the account - The exact error message or behavior you see (screenshot recommended) - Whether other users on the same account have the same problem ✅ Step 1: Confirm Your Subscription Includes These Features The Search Atlas LLM tool and AI search topic monitoring are not available on all plans. These are advanced AI features included in mid-tier and above subscriptions. 1. Click your profile icon in the top-right corner of the platform. 2. Select Billing from the dropdown (Plans & Top-ups tab). 3. Review the features listed under your active plan. If the LLM tool and topic monitoring are not listed, your current plan does not include them. You will need to upgrade to gain access. If you believe your plan should include these features based on what you were told at sign-up, proceed to Step 5 to escalate. 🔍 Step 2: Check Whether the Features Are Enabled on Your Account Even on eligible plans, features sometimes need to be manually enabled by the Search Atlas team after account creation. A feature can appear greyed out or return an access error even when your plan covers it. 1. Navigate to OTTO SEO → SEO Automation using the left sidebar (URL: /seo-automation-v3). 2. Look for the LLM tool and topic monitoring sections within this area. 3. If you see a message such as "Feature not available", "Upgrade to access", or the section is completely missing, the feature may not be toggled on for your account. This is a common cause of access issues for customers on newer accounts or accounts migrated from a previous plan. It requires account-side activation by the Search Atlas team — see Step 5. 👤 Step 3: Verify Your User Role and Permissions If you are a team member on a shared account, your user role may restrict access to certain features. Only account owners and administrators can access all platform features by default. 1. Ask your account owner or administrator to log in and check whether they can access the LLM tool and topic monitoring. 2. If the account owner can access the features but you cannot, your role needs to be updated. 3. The account owner should navigate to Settings → Team Members, locate your user profile, and adjust your permissions to grant access to AI features. If you are the account owner and still cannot access the features, your issue is not permissions-related — continue to Step 4. ⚙️ Step 4: Check for Common Setup Errors Run through this checklist to rule out configuration issues that frequently block access to these specific features: - No project or domain connected: Topic monitoring requires an active project with a connected domain. Go to Site Metrics → Site Explorer in the left sidebar and confirm at least one property is listed and verified. - Browser cache or extension conflict: Hard-refresh the platform (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) or try an incognito window. Some ad-blockers and browser extensions interfere with AI feature rendering. - Incomplete onboarding: If your account was recently created, some features unlock only after completing the initial setup wizard. Check for any pending onboarding prompts on your dashboard. - Workspace mismatch: If your account has multiple workspaces, confirm you are in the correct workspace where your plan and features are active. Switch workspaces using the dropdown at the top of the left sidebar. 🚨 Step 5: When to Escalate to the Billing or Account Team Escalate immediately — do not continue troubleshooting on your own — if any of the following are true: - Your plan billing page shows a charge consistent with a plan that should include these features, but the features are locked. - You were explicitly told at sign-up or by a sales representative that your plan includes the LLM tool and topic monitoring. - You completed Steps 1–4 and the features are still inaccessible. - You see a billing discrepancy or your plan details do not match what you agreed to at purchase. In these cases, our team needs to review your account configuration directly and can resolve feature activation issues or billing mismatches on the spot. 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.

💬 How to Locate Missing Chat History

This article explains what to do when a previous chat session is not visible in the platform. If you believe you did not delete a conversation but it is no longer appearing, the steps below will help you locate it and escalate if needed. Common Causes of Missing Chat History - Account or workspace mismatch: You may be logged into a different account or workspace than the one where the original chat took place. - Browser or cache issue: A corrupted browser cache can sometimes prevent chat history from displaying correctly. Steps to Try 1. Confirm you are signed into the correct account. If you use multiple workspaces or email addresses, log out and sign back in with the account that was active during the original chat. 2. Perform a hard refresh of the page (press Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) to clear any cached display issues. 3. Clear your browser cache and cookies, then reload the platform and check whether the chat history reappears. 4. Try accessing the platform in a different browser or an incognito/private window to rule out a local browser issue. If the Chat History Is Still Missing If the conversation does not reappear after completing the steps above, please reach out to our support team with the following information ready so we can investigate on our end: - The approximate date and time of the missing conversation - The account email address or workspace name associated with the session - A description of where in the platform you expected to find the chat history 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.

Missing Skill in Your Migration Workflow

If a skill component appears to be missing while working through a multi-stage migration process in Search Atlas, use this article to collect the right information and get targeted help from our support team. ⚠️ Why This Happens Migration workflows may involve packaged skill files or templates that are applied across multiple stages. A missing component can occur for a number of reasons — including an incomplete download, a mismatch between your account configuration and the expected package version, or a feature that has not yet been enabled for your workspace. Because the root cause varies by account, there is no single universal fix, and our team will need to review your specific setup. The most commonly reported missing component is the migration-template-builder skill, which is expected at Stage 4 of the workflow. The v1.4 package (released 2026-06-23) has been confirmed in some cases to ship with only six skill folders, leaving this component absent. The underlying feature has been completed on the engineering side, so if this skill is missing from your package, the most likely cause is that it has not yet been enabled for your specific workspace — our support team can arrange this directly. 📋 Information to Collect Before Contacting Support Having the following details ready will help our team resolve your issue faster: - The name of the missing skill or template component, exactly as it appears (or should appear) in the workflow — for example, migration-template-builder at Stage 4 - The stage or step in the migration process where the issue occurred - Whether you received or downloaded a package or file as part of this workflow, and when — including the version number if visible (for example, v1.4) - A screenshot showing the missing element or any error message displayed on screen - Your account email address and the name of the affected workspace or project 🔄 Basic Troubleshooting Steps Before reaching out, try the following to rule out common session or cache issues: 1. Refresh your browser and re-open the migration workflow from the beginning. 2. Log out of your Search Atlas account completely, then log back in. 3. Try accessing the workflow in a different browser or in an Incognito / Private window. 4. If you downloaded a package or template file, confirm the download completed without errors. If uncertain, attempt to download it again from the original source. 5. If the skill is still missing after these steps, contact our live support team with the details gathered above. ⏱️ What to Expect From Support Our team will review your account and migration workflow configuration to identify why the skill component is not available. For issues that require a deeper investigation, your case will be escalated to the relevant product team. You will be kept updated throughout the process and notified once a resolution or workaround is confirmed. 💬 Need More Help? 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.

🔍 Fix AI Summary Accuracy for Your Domain

🎯 Why Your AI Summary May Seem Inaccurate If the AI-generated summary for your site appears off-base or seems to be analysing the wrong domain, the most common cause is a misconfigured or unverified domain in your Site Explorer profile. New sites with limited data history can also produce summaries that feel generic until enough crawl data accumulates. This article walks you through how to confirm the correct domain is being analysed, how to interpret keyword difficulty for newer sites, and what SEO progress timelines you should realistically expect. ⚙️ Step 1 — Verify Your Domain Is Configured Correctly Before trusting any AI summary, confirm that Search Atlas is pointing at the exact domain you intend to analyse. 1. In the left sidebar, click Site Metrics (Site Explorer). This opens your site list at /site-explorer/list. 2. Locate your site in the list. Check that the domain shown matches your live site exactly — including whether it uses www or non-www, and https vs http. A mismatch here is the single most common cause of inaccurate AI summaries. 3. If the domain is wrong, remove the incorrect entry and add your site again using the precise URL format your site uses in the browser address bar. 4. Once corrected, allow up to 24–48 hours for the platform to re-crawl and refresh your data before re-reading the AI summary. 🔎 Step 2 — Check Keyword Data in Keyword Magic The AI summary draws heavily on keyword data associated with your domain. Thin or missing keyword data will make the summary less precise. 1. Navigate to Left sidebar → Keywords → Keyword Magic. 2. Confirm that keywords are being attributed to the correct domain. If no keywords appear, your site may be too new or may not yet have enough indexed pages for robust data. 3. Use the Keyword Gap tool (Left sidebar → Keywords → Keyword Gap) to compare your domain against competitors. This gives the AI more contextual signals to work with and often improves summary relevance. 📊 Understanding Keyword Difficulty for New Sites Keyword Difficulty (KD) scores tell you how hard it will be to rank for a given term based on the authority of pages currently ranking. For new sites, this context is essential. - KD 0–29 (Low): Best targets for new domains. Realistic ranking potential within weeks to a few months with quality content. - KD 30–59 (Medium): Achievable for newer sites with strong on-page SEO and some backlink growth. Expect 3–6 months. - KD 60–79 (High): Competitive. Usually requires established domain authority and a link-building strategy. Plan for 6–12+ months. - KD 80–100 (Very High): Dominated by high-authority domains. Not recommended as primary targets for new sites. You can review keyword difficulty scores at any time by going to Left sidebar → Keywords, which opens the Keyword Researcher at /research/keyword-researcher. Filter by KD range to build a realistic target list aligned with your current domain authority. 🚀 Realistic SEO Timeline Expectations SEO is a long-term investment. Understanding what to expect at each stage helps you interpret your AI summary and Site Explorer data accurately. - Weeks 1–4: Site gets crawled and indexed. AI summaries may be sparse. Focus on technical SEO fixes and publishing foundational content targeting low-KD keywords. - Months 2–3: Early ranking signals appear for low-competition keywords. Rank Tracker (navigate to Left sidebar → Keywords → Rank Tracker) will begin showing movement. AI summaries become more accurate as more data is collected. - Months 4–6: Consistent publishing and link acquisition start compounding. Medium-KD keyword rankings become achievable. AI summaries reflect a clearer competitive position. - Months 6–12+: Domain authority grows. High-KD keywords become realistic targets. AI summaries are most reliable and actionable at this stage. 💡 Tips to Improve AI Summary Accuracy Right Now - Ensure your sitemap is submitted and your robots.txt file is not blocking important pages. - Add as many of your target keywords as possible to the Rank Tracker — this enriches the data the AI uses to generate your summary. - Re-visit your AI summary weekly rather than daily; meaningful data shifts happen over days, not hours. - If your site recently migrated to a new domain or switched from HTTP to HTTPS, delete the old domain entry in Site Explorer and re-add the new URL to avoid mixed-data summaries. 🛠️ Still Seeing Inaccurate Results? If you have followed all the steps above and your AI summary still appears to analyse the wrong domain or shows clearly incorrect data, there may be a data ingestion issue on the platform side that our team can investigate 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.

Fix LLM Tool and Topic Monitoring Access

Overview If you are unable to add topics to monitor AI search performance or the Search Atlas LLM tool is not responding as expected, this guide covers what to check and how to get help quickly. Self-Triage Steps to Try First Before contacting support, work through the following checks — many access issues can be resolved without assistance: 1. Verify your plan includes these features. The LLM tool and AI search topic monitoring are not available on all subscription tiers. Log in to your account, navigate to your plan or subscription settings, and confirm that these features are listed as part of your current plan. 2. Check your account permissions. If you are a member of a team workspace, you may not have the role required to add topics or use the LLM tool. Ask your workspace administrator to confirm your permission level. 3. Refresh your session. Log out of Search Atlas completely, clear your browser cache, and log back in. Some access restrictions are caused by stale session data. 4. Try a different browser or disable extensions. Browser extensions — especially ad blockers or script blockers — can interfere with platform features. Test in a clean browser profile or incognito mode. 5. Check whether the issue is project-specific. If you have access to multiple projects or domains, test whether the problem occurs across all of them or only one. This helps narrow down whether it is an account-wide issue or tied to a specific configuration. What to Do If the Issue Persists If none of the steps above resolve the problem, the support team can review your account directly and help determine whether the issue is related to your current plan, a configuration setting, or something that needs to be escalated for a fix. Do not attempt to change plan or billing settings on your own while troubleshooting, as this may complicate the investigation. When you reach out, please have the following information ready so the team can investigate and resolve your issue as quickly as possible: - Your Search Atlas account email address. - The name of the project or domain you are working with. - A description of exactly what you are trying to do (for example, adding a topic to monitor or using the LLM tool). - A description of what happens — including any error messages you see, word for word. - The date and approximate time when the issue first occurred. 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.

🔗 Fix ClickUp Connector Stuck After OAuth Approval

🔍 What Is This Issue? When connecting ClickUp to your Search Atlas Coworker workspace, you may encounter a situation where the OAuth authorization window appears, you approve the connection, and then the screen shows a waiting or loading state with no further progress. The connector does not complete setup, and ClickUp remains disconnected. ⚠️ Why This Happened This was a confirmed bug in the ClickUp integration within the Coworker connector flow. The issue was reproduced by our support team and escalated to engineering. The root cause involved problems with the OAuth handling and real-time notification delivery during the connection attempt. Engineering resolved this through a series of backend fixes, including updates to the ClickUp OAuth flow, improved timeout handling, and real-time status notifications for connector attempts. ✅ Current Status This issue has been resolved. The engineering fixes have been deployed, and the ClickUp connector should now complete the OAuth authorization flow successfully. No action is required on your end beyond attempting the connection again. 🛠️ Steps to Reconnect ClickUp 1. Log in to your Search Atlas account and navigate to the Coworker section. 2. Go to the Connectors area and locate the ClickUp integration. 3. Start the connection process. The OAuth authorization window will open. 4. Approve the requested permissions in the ClickUp authorization window. 5. Wait a few seconds for the platform to confirm the connection. The connector should now show as connected without hanging. 6. If the connector shows as connected, you are all set and can begin using ClickUp within Coworker. 🔄 If the Issue Still Occurs While this bug has been marked resolved, if you are still experiencing a hanging or stuck state after completing OAuth approval, try the following before contacting support: - Refresh the page after approving access and check whether the connector status has updated. - Clear your browser cache and cookies, then attempt the connection again in a clean browser session. - Try a different browser to rule out a browser-specific compatibility issue. - Check your pop-up blocker settings to ensure the OAuth window is not being silently blocked or interrupted mid-flow. - Revoke the Search Atlas app permissions in your ClickUp account settings, then retry the connection from scratch to start with a clean authorization state. 💬 Need More Help? If you have followed all the steps above and the ClickUp connector is still not connecting, our team wants to hear from you so we can investigate further. 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.

Fix GBP Lock Errors and Missing Social Fields

🔍 Overview Two common issues can interrupt your GBP Golden Loop progress in Search Atlas: a lock error that prevents your profile from staying locked, and a validation blocker when a client does not have every social media account or optional attribute listed in the checklist. This article explains why these happen and what to do next. ⚠️ Understanding the GBP Lock Error When you attempt to lock a GBP project in Search Atlas, you may encounter errors or find that the lock does not hold as expected. These issues can be caused by Google-side restrictions on certain address fields or by platform-level behaviour affecting how location data is saved. Because the exact cause can vary by account and location, our team will need to investigate your specific project. 🛠️ What to Do When the GBP Lock Fails If you are experiencing a GBP lock error or the lock is not persisting on your project, please escalate to our support team so we can investigate. To help us resolve this as quickly as possible, have the following ready before reaching out: - The name of the affected GBP project in Search Atlas. - The exact error message you are seeing (copy it word for word if possible). - The timestamp or approximate time when the error first occurred. - Whether the lock appears to save initially but then resets, or whether it fails immediately. - Any recent changes made to the address or profile fields before the error appeared. 📋 Handling Missing Social Media Accounts The Golden Loop checklist may include social media profile URLs (such as Facebook, Instagram, X, LinkedIn, or others) as required fields. If a client does not have one or more of these accounts, the checklist item may block you from marking the profile as complete. Because the available options for handling missing fields depend on how your specific checklist is configured, our team can advise on the correct approach for your account. When escalating, please include: - The name of the GBP project and the specific checklist field that is causing the blocker. - Whether the client has confirmed they will not be creating the missing social account. - A screenshot of the checklist item and any options currently visible to you. 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.

🔧 Fix Stalling Approvals in Slack and Dashboard

Overview Some users have experienced a frustrating issue where approval actions sent through Slack or the Search Atlas Dashboard appear to stall indefinitely — hitting approve has no effect, and the workflow never moves forward. This article explains what caused the issue, how it was resolved, and what to do if you encounter similar behavior. What Caused This Issue This problem was traced to a confirmed engineering bug affecting the approval flow for AI agent and Coworker workflows. The bug caused approval actions to fail silently: the system appeared to accept your approval, but nothing executed behind the scenes. No status update was sent to Slack or the Dashboard, leaving the workflow stuck with no indication of what went wrong. This issue has since been identified and resolved by the engineering team. Current Status The engineering team has completed the fix. If you were affected by this bug, approval actions through both Slack and the Search Atlas Dashboard should now work reliably. No action is required on your end to apply the fix — it was deployed automatically. Steps to Verify Everything Is Working 1. Open the Search Atlas platform and navigate to your AI agent or Coworker workflow area. 2. Trigger or locate a pending approval action in your workflow. 3. Submit your approval and wait a moment for the system to respond. 4. Check whether the workflow advances as expected — either in the Dashboard or in your connected Slack channel. 5. If the action completes successfully, no further steps are needed. If You Are Still Experiencing Stalling If approval actions are still not moving forward after the fix, try the following before contacting support: - Refresh your browser and retry the approval. Occasionally a stale session can cause the interface to appear unresponsive even when the backend is functioning. - Clear your browser cache and reload the platform, then attempt the approval again. - Check your Slack connection within the Search Atlas Dashboard to confirm your Slack integration is still active. If it appears disconnected, use the available option to reconnect it. - Try approving from a different surface — if the action is stalling in Slack, attempt it directly from the Search Atlas Dashboard, or vice versa. - Wait a few minutes and retry. Transient network or service interruptions can occasionally delay responses. If the action processes after a short wait, no further action is needed. What to Include If You Need Further Help If you are still experiencing stalling after trying the steps above, please reach out to our support team. Include your account details, a description of the workflow involved, and the surface where the stalling is occurring (Slack, Dashboard, or both). If you need assistance, you can contact us through the Search Atlas support channel.

⚠️ LLM-Powered Analysis Features Stuck in Pending State

We are aware of an ongoing issue affecting LLM-powered analysis features — brand research, brand info, topics, queries, and competitor analysis — that began around May 29. Analyses may appear stuck in a pending or loading state and will not return results; no action is needed on your end. 🔍 What's Happening Since approximately May 29, the LLM analysis pipeline that powers several Search Atlas features has been interrupted. Affected features display results as permanently pending or loading with no output delivered. The following features are currently affected: - Brand Research - Brand Info - Topics - Queries - Competitor Analysis If you submitted any of these analyses on or after May 29, your job is queued and will be processed automatically once service is restored. You do not need to re-submit. 🛠️ Workaround Steps There is currently no workaround available for this issue. Do not re-submit your analyses — resubmitting will not resolve the problem and may create duplicate entries in the processing queue. All queued analyses will run automatically when the pipeline is restored. 📡 Engineering Status Our engineering team is investigating the root cause and is actively working to restore the pipeline. All analyses submitted since May 29 will be processed once service resumes — no data or requests will be lost. This article will be updated as soon as the fix is deployed and results begin delivering to affected accounts. We will provide an estimated timeline as soon as we have more information. 📞 When to Contact Support Reach out to our support team via the in-app chat if any of the following apply: - You have a time-sensitive deadline that cannot wait for the pipeline to restore. - You see no resolution or status update after 24 hours. - You are experiencing a separate issue not described on this page. When you contact support, include your account name and the date you submitted the affected analysis so the team can assist you faster. 🌀 Our team is fully engaged on restoring the pipeline and will process all queued analyses as soon as service resumes — we sincerely apologize for the disruption and appreciate your patience.