Troubleshooting

Stay organized with collections Save and categorize content based on your preferences.

Filter this document's content by the agent type tag:

Filter this document's content by the category tag:

API call gets permission denied

Agent type tags: CX, ES
Category tags: API, Auth

Issue

Received PERMISSION_DENIED response for API call.

Solution

Ensure you have set up (CX, ES) authentication and roles correctly. In particular, ensure you have done the following:

  • Created a service account and did not accidentally delete it.
  • Provided the service account with a role that grants permission to call the desired method.
  • Downloaded the service account private key file.
  • Set the GOOGLE_APPLICATION_CREDENTIALS environment variable to the private key file.

API call mentions unknown project

Agent type tags: CX, ES
Category tags: API, Project

Issue

Received Dialogflow API has not been used in project 32555940559 error for API call.

Solution

Ensure you have done the following:

  • Set the GOOGLE_APPLICATION_CREDENTIALS environment variable (see PERMISSION_DENIED).
  • Provided the correct project ID to the API call.

API call gets invalid authentication credentials error

Agent type tags: CX, ES
Category tags: API, Auth

Issue

Received Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. response for API call.

Solution

This may be due to manually creating credentials with your client library while specifying a non-default region. See one of the following for guidance:

API call response requests a switch to a different host

Agent type tags: CX, ES
Category tags: API, Auth

Issue

Received Please switch to 'REGION-dialogflow.googleapis.com' to access resources located in 'REGION' response for API call, where REGION is a specific region ID.

Solution

This happens when you specify the region in the request, but not the endpoint. See one of the following for guidance:

Missing fields in the API call response

Agent type tags: CX, ES
Category tags: API

Issue

Some fields are missing in the API response.

Solution

If you expect a numeric value for a specific field in the API response, the field may be absent from the response if the returned value is 0.

For more information on the default value behavior (including non-numeric values), see:

Unable to delete project because of lien

Agent type tags: ES
Category tags: Project

Issue

When trying to delete a GCP project, you get a notification that the project cannot be deleted because it has liens, and one of the liens is related to Dialogflow.

Solution

  1. Make sure that the Dialogflow ES agent linked to the project has been deleted.

    Dialogflow ES Console

    Open https://dialogflow.cloud.google.com/#/agent/project-id/intents. If you get a notification that the agent doesn't exist, this means that it has been deleted. Otherwise, check if you no longer need the agent and delete it.

    Dialogflow API

    Use the search method of the agent type.

  2. Get the lien name.

    gcloud

    Use the gcloud alpha resource-manager liens list command, as described in the Listing liens on a project documentation.

    API Explorer

    Use the Try this API panel on the Method: liens.list page:

    • Fill out the parent field, as suggested in the parameter description.
    • Click Execute.
  3. Delete the lien.

    gcloud

    Use the gcloud alpha resource-manager liens delete LIEN_NAME command, as described in the Removing liens from a project documentation.

    API Explorer

    Use the Try this API panel on the Method: liens.delete page:

    • Fill out the name field with the lien name that you got at step 2.
    • Click Execute.
  4. Shut down the project.

Console fails to set up project

Agent type tags: ES
Category tags: Console, Project

Issue

Received Failed to set up GCP project error when creating an agent with the console.

Solution

You may not have permission to create GCP projects. Check if you can create a GCP project directly from the GCP Console. If you are not able to create a project, follow the recommendations provided in the error message.

Console fails agent creation when API has not been enabled

Agent type tags: CX
Category tags: Console

Issue

Received Dialogflow API has not been enabled for the project. Code: FAILED_PRECONDITION error when creating an agent with the console.

Solution

Follow the setup steps to enable the Dialogflow API.

When attempting to access console from organization account, receive service error

Agent type tags: CX, ES
Category tags: Console

Issue

Received You don't have access to this service error when attempting to access the console from your organization account.

Solution

Contact your organization's system administrator, and verify that your organization's settings provide access to the console.

If your organization's settings should allow access, and you migrated your account from a different organization, your account may have been flagged as restricted by Google. This is likely the problem if other users in your organization can access the console, but you cannot. Contact support to get assistance.

Phone gateway connectivity

Agent type tags: ES
Category tags: Integration

Issue

When using phone gateway, you get a busy signal or the call drops.

Solution

There are quotas and limits for this feature. If you receive a busy signal or the call drops, you may have exceeded your quota.

Dialogflow CX Messenger no response

Agent type tags: CX
Category tags: Integration

Issue

No agent response for Dialogflow CX Messenger interactions.

Solution

If you are not seeing any responses from Dialogflow Messenger, make sure that billing is enabled on the project and the Dialogflow API is enabled on the project. See the setup instructions.

Entity value still matched after synonym deletion

Agent type tags: CX, ES
Category tags: NLU

Issue

After a synonym has been deleted from an entity and the agent has been retrained, this synonym is still extracted as a parameter value for this entity.

Solution

The synonym may be present in the agent as an implicit entity (CX, ES). Find all the intents that have annotations with this parameter. Make sure that none of these annotations are applied to the text representing the deleted synonym.

Voice bot skips some responses

Agent type tags: CX
Category tags: Text-to-Speech

Issue

For an agent designed for both text and voice, the voice bot does not read some of the responses.

Solution

If at least one output audio text response is defined for a particular conversation turn, make sure that the output audio text option is consistently present thorughout the agent's fulfillment and webhook responses at all steps for this conversation turn.

SSML tags don't take effect

Agent type tags: CX, ES
Category tags: Text-to-Speech

Issue

SSML tags are defined in the agent fulfillment, but the voice bot reads the synthesized text without SSML effects.

Solution

Make sure that only one <speak></speak> pair is present per one response card in the Dialogflow console or per one response message object if responses are supplied via the API or webhook.

Unexpected synthesized pronunciation

Agent type tags: CX, ES
Category tags: Text-to-Speech

Issue

Synthesized pronunciation of agent responses (for example, proper names, acronyms) is not as expected.

Solution

To guarantee particular pronunciations for not commonly known words, use the SSML say-as or phoneme tag in agent responses.

Reached the maximum allowed state machine execution steps

Agent type tags: CX
Category tags: Runtime

Issue

Received the following error message in the Dialogflow CX consnole or in the logs when sending runtime requests to the agent:

You have reached the maximum allowed state machine execution steps. You may consider simplifying your agent/flow design. Current execution steps are: [<array_of_objects>]

The array in the error message contains a list of execution steps for the request. The list may be incomplete if the number of steps is too large.

Solution

This error message usually indicates that the number of transitions for a single conversation turn is too large. A common example is transitioning to the same page, which creates an infinite loop.

To solve the issue:

  1. Copy the JSON array from the error message.
  2. (Optional) Format the copied array as pretty JSON for better readability. If the error message is truncated, search for the last "Step" object, delete the incomplete step object and the preceding comma, and add a closing array bracket befory validating and prettifying the JSON.
  3. Look at the "TriggeredTransitionRouteId" and "TargetPage" values for each step. In the case of infinite loop, the "TriggeredTransitionRouteId" and "TargetPage" fields have repeating values for most of the steps.
  4. Modify your agent design to remove the infinite loop transitions or to reduce the number of transitions for a single conversation turn.

Regular expression match is too broad

Agent type tags: CX, ES
Category tags: Regex

Issue

Received an error Regular expression match is too broad when creating a regexp entity (CX , ES).

Solution

Consider the following approach:

  • Use ^ and $ in the regular expression to indicate the beginning and the end of text respectively.
  • Use the regexp entity with a required parameter (CX, ES)
  • Define the required parameter prompts to ask the end-user to provide only the entity value without any surrounding words.

Inaccurate alphanumerics speech recognition by regexp entities

Agent type tags: CX, ES
Category tags: Speech-to-Text, Regex

Issue

Received inaccurate transcripts for voice inputs of alphanumerics designed to be matched to a regexp entity (CX , ES).

Solution

  1. Make sure that speech adaptation is enabled in the agent settings (CX, ES).
  2. Make sure that at least one entity entry follows all the regex entry requirements (CX, ES).
  3. For specific patterns, use the most specific regular expressions. For example, for an alphanumeric that starts with two letters followed by five digits, use [a-zA-Z]{2}\d{5} instead of [a-zA-Z0-9]{7}.
  4. Make sure that your regexp entity allows for matching non-alphanumerics (spaces, dashes, and so on.) that may be inserted by the speech recognizer. To meet the requirement #2 from this list, create multiple entity entries: one entry to satisfy the requirements #2 of this list and another one to account for non-alphanumeric. For example, to match five digits and allow for non-alphanumerics:
     \d{5}
     (\d[^a-zA-Z0-9]*){5}
    
  5. Make sure that your agent follows the parameter definition requirement (CX, ES).

    Example for CX

    Required parameter in CX

    Example for ES

    Required parameter in ES
  6. Make sure that your agent follows the training phrases annotation requirement (CX, ES).

    Example for ES

    No annotations in training phrases in ES
  • Make sure that your tests follow the testing guidelines (CX , ES).
  • To remove non-alphanumeric characters that may have been inserted by the speech recognizer, use the following:
  • Check speech adaptation limitations (CX , ES).
  • Undesired non-alphanumerics inserted by speech recognition

    Agent type tags: CX, ES
    Category tags: Speech-to-Text

    Issue

    When trying to match alphanumerics, undesired non-alphanumerics characters (spaces, dashes, and so on.) are inserted by the speech recognizer, which results in the entity not being matched.

    Solution

    1. If you use system entities for matching numbers, consider using regexp entities (CX , ES) instead.
    2. Follow all the recommendations from the section above: Inaccurate alphanumerics speech recognition by regexp entities.
    3. For matching numbers via telephony integrations, consider a DTMF option in addition to voice recogniotion.