QID fails to match when using multi-language with dedicated intents

[amendlik]

Describe the bug
When configured with ENABLE_MULTI_LANGUAGE_SUPPORT=true, QIDs with a dedicated intent only match in English. Other languages fall through to the no_hits QID.

NoHits-Only configuration

Steps

1. Install QnABot with a Bedrock Knowledge Base configured
2. Define only one QID for no_hits

Export

{
  "qna": [
    {
      "a": "No hits",
      "type": "qna",
      "qid": "TEST-nohits",
      "q": [
        "no_hits"
      ]
    }
  ]
}

In the web client

Human: How do I pay a parking ticket?
Bot: No hits
Human: ¿Cómo pago una multa de estacionamiento?
Bot: Sin visitas

SUCCESS: This configuration works as expected.

QID Match

Steps

1. In the Designer, click the Add button
2. Set the Document Type to qna
3. Set the Item ID to TEST-parking
4. Add an utterance: How do I pay a parking ticket?
5. Add an answer: Go to the website

Export

{
  "qna": [
    {
      "a": "Go to the website",
      "type": "qna",
      "qid": "TEST-parking",
      "q": [
        "How do I pay a parking ticket?"
      ]
    }
  ]
}

In the web client

Human: How do I pay a parking ticket?
Bot: Go to the website

Human: ¿Cómo pago una multa de estacionamiento?
Bot: Ir al sitio web

SUCCESS: This configuration works as expected.

Failure Scenario

Steps

1. Edit TEST-parking
2. Expand Advanced
3. Set Create a dedicated bot intent for this item during LEX REBUILD to Checked
4. Click Save
5. Click LEX REBUILD

Export

{
  "qna": [
    {
      "a": "Go to the website",
      "enableQidIntent": true,
      "type": "qna",
      "qid": "TEST-parking",
      "q": [
        "How do I pay a parking ticket?"
      ]
    }
  ]
}

In the web client

Human: How do I pay a parking ticket?
Bot: Go to the website

Human: ¿Cómo pago una multa de estacionamiento?
Bot: Sin visitas

FAILURE: This configuration works as expected in English, but falls through tono_hits in Spanish.

Please complete the following information about the solution:

• Version: [e.g. v6.1.5]
• Region: [e.g. us-west-2]
• Was the solution modified from the version published on this repository? No
• If the answer to the previous question was yes, are the changes available on GitHub?
• Have you checked your service quotas for the services this solution uses? Yes
• Were there any errors in the CloudWatch Logs? No

[abhirpat]

Thank you for reporting this. We will revert back to you.

[amendlik]

@abhirpat Can you clarify the next steps for this issue, please? Is there something more you need me to do at this time?