🔍 Overview
When you attempt to deploy all changes to your Google Business Profile (GBP) inside Search Atlas, you may see a Deployment Failed — ATTRIBUTE_INVALID_ENUM_VALUE error. The deploy does not complete, and refreshing or clearing your browser cache does not resolve the issue.
This error is caused by a deprecated attribute value stored against your GBP location — specifically, Google's Business Profile API no longer accepts certain attribute values (for example, attributes/preferred_messaging_service set to facebook_messenger). Because Google rejects this value at the API level, all deploys for the affected location are blocked until the value is removed or corrected on the backend.
⚠️ What Causes This Error
- One or more GBP attributes linked to your location contain a value that Google's API has deprecated and no longer accepts.
- This is a backend data issue — it cannot be fixed by refreshing the page, clearing your browser cache, or using a different browser.
- The problem affects the entire location, so all pending changes are blocked until the invalid attribute is resolved.
✅ What You Should Do
- Confirm the error message. Make a note of the exact error text you see (e.g., Deployment Failed — ATTRIBUTE_INVALID_ENUM_VALUE) and the GBP location name it affects.
- Check your GBP attributes in Google Business Profile directly. Log in to your Google Business Profile account at business.google.com and navigate to the affected location. Look for any messaging or communication-related attributes (such as a preferred messaging service). If you see Facebook Messenger or another deprecated messaging option listed, remove it and save the change. This may clear the deprecated value on Google's side and unblock your deploy.
- Retry the deploy in Search Atlas. After removing any suspect attributes in Google Business Profile, return to Search Atlas and attempt to deploy your changes again. Wait a few minutes before retrying to allow Google's API to reflect the update.
- If the deploy still fails, contact the Search Atlas support team using the chat widget (see below). Share the name of the affected GBP location and a screenshot or copy of the error message. Our engineering team will identify and remove the deprecated attribute value from the backend, which will unblock your deploys.
📊 What Happens After You Report It
Once you reach out, our team will investigate the specific attribute causing the conflict on your location's profile. The fix involves removing or replacing the deprecated value on the backend — no action is required from you on the Google side beyond the steps above. After the fix is applied, your deploys will resume normally.
If you need further help, please reach out to our support team via the chat widget in Search Atlas.