"mybusiness.googleapis.com" Error Message

"mybusiness.googleapis.com" Error Message




This issue occurs when Google's API is not working, or their server is down. 

Resolution: 
Attempting to resend the response at a later time should then result in it successfully posting to Google.

To resend a response, simply delete the response from the outbox and respond again in the inbox.

If after another attempt you receive the same error message again, please contact us at support@localclarity.com to escalate this issue.



    • Related Articles

    • "Internal error encountered" Error Message

      This error is caused by Google server issues; There is no insight shared by Google as to its exact cause, but we understand it to be the cause of some database/server/connection issue in Google.  Resolution:  ​ The next step to resolve this issue is ...
    • "Read timed out" Error Message

      If you receive this error message in your Outbox, it is most likely a result of after 4 automated retries to send the response through, Google servers remain busy. Resolution:  The next step to resolve this issue is to delete the response from the ...
    • "The service is currently unavailable" Error Message

      If you receive this error message in your Outbox, it is most likely a result of after 4 automated retries to send the response through, Google servers remain busy. Resolution: The next step to resolve this issue is to delete the response from the ...
    • "The service is currently unavailable" Error Message

      If you receive this error message in your Outbox, it is most likely a result of 4 or more automated retries to send a response through, indicating that the Google servers are remaining busy. Resolution: The next step to resolve this issue is to ...
    • "Insufficient permissions to access the resource" Error Message

      If you've received this error message in your Outbox it is because you no longer have access to that location. Resolution: This can happen for any number of reasons, but there are a two options to address and resolve this issue, Check internally ...