## 🧭 Overview

When you run a GBP audit, processing usually begins immediately and the audit status is tracked on screen. If the status has not updated after several minutes, the audit is likely stuck in a pending state. This is typically caused by a temporary background worker outage on Search Atlas's infrastructure — not by anything wrong with your account or your Google Business Profile.



## ⚠️ How to Recognise This Issue

- You triggered a GBP audit and the status appeared but has not advanced for 5 or more minutes.
- The audit status remains **Pending** with no error message displayed.
- Other parts of the platform continue to work normally.

## 🛠️ What Causes It

GBP audits are processed by a dedicated background worker. If that worker goes offline or becomes overloaded, audit tasks queue up and cannot progress until the worker is restarted by our engineering team. This is an infrastructure-level issue that cannot be resolved by changing settings inside your account.



## ✅ Steps to Take

1. **Wait 10–15 minutes.** Our monitoring systems detect worker outages automatically, and engineering teams are alerted to restart the worker as quickly as possible. In most cases the audit resumes on its own once the worker is back online.
2. **Refresh the page.** After waiting, navigate back to your GBP project and check whether the audit status has updated.
3. **Do not submit the audit again.** Triggering a second audit for the same profile while the first is pending can create duplicate tasks and delay resolution further.
4. **Check back after 30 minutes.** Once engineering restarts the worker, queued audits are automatically re-dispatched and should complete in the normal timeframe.
5. **If the audit is still stuck after 30 minutes,** contact our support team so they can escalate to engineering directly (see below).

## 📋 Information to Have Ready When Contacting Support

To help our team investigate quickly, please have the following details available before reaching out:

- The name of the GBP profile or project you were auditing.
- The approximate time you triggered the audit.
- A confirmation that the audit status has not changed for more than 30 minutes.

## 💡 What Happens Behind the Scenes

When our engineering team is alerted, they restart the background worker responsible for processing GBP audit tasks. Once the worker is online, a recovery process automatically re-dispatches any audits that were stuck in the queue. You do not need to do anything for the audit to resume — it will pick up and complete without you having to retrigger it.



## 💬 Need Further Help?

If the audit remains stuck after 30 minutes, please reach out to our support team and we will escalate to engineering on your behalf.