Troubleshoot
This section describes common issues that you can encounter.
App is not responding
If you message the Chat app and it responds "App is not responding," verify the Chat app's configuration:
In the Google Cloud console, click Menu > Cloud Functions.
Click the function's name.
Click Edit.
Under Connection Settings, make sure that you selected App URL. Also make sure that the App URL matches the Trigger URL of your Cloud Function.
Under Functionality, make sure that you selected App can be messaged directly.
Google Chat API is only available to Google Workspace users
When configuring the Chat app for publication, you might receive the error
Google Chat API is only available to Google Workspace users. This message
means that your Google account isn't part of a Google Workspace domain. Chat apps are only available in Google Workspace domains, so you must have a
Google Workspace account.
Function ChatApp in region us-central1 in project chatappproject already exists
When deploying a Cloud Function, you might receive the error Function
ChatApp in region us-central1 in project chatappproject already
exists. This message means that another Cloud Function has the same name as the
one you're deploying. Change the name, and
deploy the function again. Verify that the Chat app uses the Trigger URL for
your Cloud Function, not the Trigger URL of the preexisting Cloud Function.
One or more users named in the policy do not belong to a permitted customer
When deploying a Cloud Function, you might receive the error The operation
cannot be completed on the function: "One or more users named in the policy do
not belong to a permitted customer." If you get this error and then message the
Chat app, you get an error saying that the app is not responding because Google
Chat can't reach the server hosting the Cloud Function. This message means that
a user named "allUsers" doesn't have permission to call the Cloud Function.
Giving "allUsers" the "Cloud Functions Invoker" role means that the Cloud
Function that powers the app is publicly available and accessible without
authentication. To learn how to assign a role, see
Grant a single role.
This error might mean that the Google Cloud project is domain restricted. For more information about domain restriction constraints, refer to Restricting identities by domain.
To resolve this issue, verify that your Cloud Function allows unauthenticated invocations. To learn how to allow unauthenticated invocations for an existing Cloud Function, refer to Allowing public (unauthenticated) access.
Users can be excluded from spaces
If a Google Workspace administrator disallows users to turn Chat history on or off, then there might be times when users can't join or stay in a space due to a conflict between a user-level setting that forces chat history on or off and a space that inherits the organization-level forced setting.
For example, if a user has a Chat history setting forced "on" and a space has a Chat history setting forced "off", then that user might not be able to join the space. Additionally, that user might be removed from the space if they joined prior to the conflict and then they post a message in the space after the conflict.
In the above scenarios, and other scenarios where there are conflicts between history settings, Chat API might not be able to create a membership, or creating a message with user authentication might remove the authenticated user with a conflicting Chat history setting from the space.
To learn more, see Users can be excluded from spaces in the Google Workspace Admin Help center.