vania-janet/multiturn-rag-retrieval-data huggingface dataset:
IBM Cloud Network Load Balancer for VPC limitations 

Known limitations for IBM Cloud® Network Load Balancer for VPC (NLB) are as follows:



* The NLB requires the member and port combination to be unique. In other words:



* A member with instance X and port Y cannot be added to a pool of NLB A, if a member with instance X and port Y exists in a pool of NLB B.



* An NLB member VSI’s port can only be used for NLB traffic.
* There is a one-to-one mapping between listener and pool.
* The NLB uses the primary network interfaces of its associated members for data traffic. Non-primary network interfaces are not supported.
* To ensure service availability, use a dedicated subnet with your NLBs. Clients and members should reside in an alternate subnet.
* Two members with the same instance X and port Y cannot exist at the same time for an NLB. In this case, your traffic will not route correctly.
* For an NLB with routing mode enabled:



* The only supported back-end targets are VNF instances. When using APIs, the listener port_min and port_max should be set to 1 and 65535 respectively; port should be left empty.
* Only one listener is supported.
* The NLB and the VNF back-end targets must be in the same subnet.



* The default load balancer quota is 50 per region. To increase the number, you must [create a support case](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case).
* When you create a listener for a network load balancer, you can specify a protocol of tcp or udp. However, each listener in the network load balancer must have a unique port.
* For Private NLB, the NLB service might add rules to custom routing tables to ensure service availability for some failure conditions. As a result, if the client is outside the zone and/or VPC of the NLB, you must add an ingress custom routing table to the VPC where the NLB resides with the proper traffic source selected.
Why am I receiving the Status Code - "429 Too Many Requests" as response to the API Calls? 

  What’s happening 

API requests to App Configuration service is returning the HTTP status code as 429.

  Why it’s happening 

All the APIs of the App Configuration service are rate-limited. Excessive number of requests sent to App Configuration from a single source will be blocked if they exceed the threshold value within a specific time period.

  How to fix it 

Evaluate the reason of the excessive requests being sent to App Configuration exceeding the threshold value. Also, you may retry the request again after the interval specified in the retry-after response header.
"assistant_phone_number":"+18885556789"
}







 whatsapp 

Included only if the WhatsApp integration is in use.



 Properties 

Properties contained in the private object are treated as private variables, which are not included in logs.



Properties of the whatsapp object

 Name Type Description 

 assistant_phone_number String The phone number associated with with the Watson Assistant end of the conversation. 
 private.user_phone_number String The phone number from which the customer's WhatsApp message originated. 







 Example JSON 

"whatsapp": {
"private":{
"user_phone_number":"+18595553456"
},
"assistant_phone_number":"+18885556789"
}







 slack 

Included only if the Slack integration is in use.



 Properties 



Properties of the slack object

 Name Type Description 

 team_id String The unique identifier of the Slack team. 
 channel_id String The unique identifier of the Slack channel. 







 Example JSON 

"slack": {
"team_id":"T02F3KE542J",
"channel_id":"C4K3KTTRD"
}







 facebook 

Included only if the Facebook integration is in use.



 Properties 

No additional properties.





 Example JSON 

"facebook": {}







 teams 

Included only if the Microsoft Teams integration is in use.



 Properties 



Properties of the teams object

 Name Type Description 

 conversation_id String The unique identifier of the Microsoft Teams conversation. 







 Example JSON 

"teams":{
"conversation_id":"a:1ATy08jyGkPGy2QdKIrGZL5u_o6fIUVDRKeIZtkIUAkQDC23FC9S97f18i-UNl-eISAfDWqoQeTbregvSE8jK0LNy6h9VssNcN3CsGG9guMiUB0EeSqxnnEFpAVzbkayR"
}
Network load balancers (NLB) <br><br> * You can't update an existing NLB from version 1.0 to 2.0. You must create a new NLB 2.0.<br> * You can't create subdomains for private NLBs.<br> * You can register up to 128 subdomains. This limit can be lifted on request by opening a [support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar).<br><br><br> 
 strongSwan VPN service See [strongSwan VPN service considerations](https://cloud.ibm.com/docs/openshift?topic=openshift-vpnstrongswan_limitations). 
 Service IP addresses You can have 65,000 IP addresses per cluster in the 172.21.0.0/16 range that you can assign to Kubernetes services within the cluster. 
 Subnets per VLAN Each VLAN has a limit of 40 subnets. 







 Storage 

Keep in mind that the [service](https://cloud.ibm.com/docs/containers?topic=containers-limitationstech_limits) limitations also apply.



Classic cluster storage limitations

 Category Description 

 Volume instances You can have a total of 250 IBM Cloud infrastructure file and block storage volumes per account. If you mount more than this amount, you might see an "out of capacity" message when you provision persistent volumes. For more FAQs, see the [file](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-file-storage-faqsprovision) and [block](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-block-storage-faqsauthlimit) storage docs. If you want to mount more volumes, [contact IBM Support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar). In your support ticket, include your account ID and the new file or block storage volume quota that you want.
For more information, check out the [Vonage documentation](https://api.support.vonage.com/hc/en-us/articles/217571017-What-is-a-Sender-ID).







 With the GUI 

To configure MFA with the GUI, check out [Cloud Directory](https://cloud.ibm.com/docs/appid?topic=appid-cloud-directory).



1. Navigate to the Cloud Directory > Multifactor authentication tab of the App ID dashboard.
2. In the Enable multifactor authentication box, on the settings tab, toggle MFA to Enabled. Acknowledge that you understand that MFA is charged as an [advanced security event](https://cloud.ibm.com/docs/appid?topic=appid-pricing).
3. Select SMS as your Authentication method.
4. In the SMS channel tab, configure your Vonage account information.



1. If you don't already have an account with Vonage. Create one.
2. From the Vonage dashboard, click SMS.
3. In the Code it yourself section, copy your API key and paste it in the key box in the App ID dashboard.
4. Copy the API secret in the Vonage dashboard and paste it in the Secret box in the App ID dashboard.
5. Enter [the ID](https://api.support.vonage.com/hc/en-us/articles/217571017-What-is-a-Sender-ID) that you want to send messages from. A valid number format follows the [E.164 international numbering format](https://en.wikipedia.org/wiki/E.164). For example, a US number takes the form +19998887777. You must specify both the country code, starting with a + symbol and the national subscriber number. In some countries, Vonage supports alpha-numeric sender IDs. App ID uses the value that you enter as Vonage's sender ID.
button.innerHTML = 'Fill in account number';
button.addEventListener('click', () => {
// Look for the account number element in the document and fill in the account number.
document.querySelector('account-number').value = '1234567';
});

element.appendChild(button);
}
2. In your onLoad event handler, use the [on()](https://web-chat.global.assistant.watson.cloud.ibm.com/docs.html?to=api-instance-methodson) instance method to subscribe to the customResponse event, registering the handler as the callback. This enables the assistant to send a custom response that displays the button for filling in the account number.

instance.on({
type: 'customResponse',
handler: (event, instance) => {
const { message } = event.data;
if (message.user_defined &&
message.user_defined.user_defined_type === 'fill_account_number') {
accountNumberResponseHandler(event, instance);
}
},
});

In this example, we are checking the custom user_defined_type property of the custom response, and calling the accountNumberResponseHandler() function only if the specified type is fill_account_number. This is an optional check that shows how you might use a custom property to define multiple different custom responses (each with a different value for user_defined_type).



For complete working code, see the [Page interactions for Watson Assistant web chat](https://github.com/watson-developer-cloud/assistant-toolkit/tree/master/integrations/webchat/examples/page-interaction) example.
The command_info.type field can specify any of the following supported commands:



* collect: Collects DTMF keypad input.
* disable_barge_in: Disables DTMF barge-in so that playback from the phone integration is not interrupted when the customer presses a key.
* enable_barge_in: Enables DTMF barge-in so that the customer can interrupt playback from the phone integration by pressing a key.
* send: Sends DTMF signals.



For detailed information about how to use each of these commands, see [Handling phone interactions](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-phone-actions).





 Example 

This example shows the dtmf response type with the collect command, used to collect DTMF input. For more information, including examples of other DTMF commands, see [Handling phone interactions](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-phone-actions).

{
"generic": [
{
"response_type": "dtmf",
"command_info": {
"type": "collect",
"parameters": {
"termination_key": "",
"count": 16,
"ignore_speech": true
}
},
"channels":
{
"channel": "voice_telephony"
}
]
}
]
}
Show more







 end_session 

Sends a command to the channel ending the session. This response type instructs the phone integration to hang up the call.



 Integration channel support 



 Phone SMS 

 ![Yes](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/checkmark-icon.svg) 





* The SMS integration supports ending a session by using the terminateSession action command.







 Fields 



 Name Type Description Required?
Enable secure access on an existing instance 

To enable secure access on an existing instance, navigate to the Secure access setting on the Instance details page of your instance.







 Set the metadata hop limit by using the UI 

You can set the hop limit for IP response packets from the metadata service. The hop limit can be any value from 1 (default) to 64. The metadata service must be enabled.



 Set the metadata hop limit when you provision an instance 

To set the hop limit when you provision an instance, go to the Hop limit setting in the Metadata window when you Create an instance from the Virtual server instances for VPC page. Specify a hop limit value between 1 and 64.





 Set the metadata hop limit on an existing instance 

To set the hop limit on an existing instance, go to the Hop limit setting setting on the Instance details page of your instance. Specify a hop limit value between 1 and 64.









 Configure metadata settings by using the CLI 

You can enable and disable features of the metadata service using the CLI.

The following example shows an instance with the metadata service enabled.

$ ibmcloud is instance instance-name -q

ID 0716_9cc6d74d-4b77-4cca-b1f4-31cc6edefe01
Name instance-name
CRN crn:v1:staging:public:is:us-south-1:a/af6443f619a949c9919c1eb1625d6cc5::instance:0716_9cc6d74d-4b77-4cca-b1f4-31cc6edefe01
Status running
Availability policy on host failure restart
Startable true
Profile bx2-2x8
Architecture amd64
vCPUs 2
Memory(GiB) 8
Bandwidth(Mbps) 4000
Volume bandwidth(Mbps) 1000
Network bandwidth(Mbps) 3000
Lifecycle Reasons Code Message
- -

Lifecycle State stable
Metadata service Enabled Protocol Response hop limit
false http 1

Image ID Name
Rules for creating custom entries 

The following rules and guidelines apply to populating a custom model with custom entries (word/translation pairs).



 Maximum custom entries and limits 

The following limits apply to all custom models and entries:



* A word in a custom entry can contain a maximum of 49 characters.
* A translation in a custom entry can contain a maximum of 499 characters.
* A custom model can include a maximum of 20,000 custom entries.
* A custom model can include a maximum of 1000 custom prompts.







 Character encoding 

The service accepts ASCII and UTF-8 character encoding for word and translation entries. For translations, use ASCII encoding for SPR notations and UTF-8 encoding for IPA notations.





 White space 

A word cannot include white space. The service uses white space to delineate individual words in the input text.





 Case-sensitivity 

A word is case-sensitive. For example, assume that a custom model contains the entry {word='Sun', translation='Sunday'}. The service applies its default pronunciation to the word sun but the custom translation to the word Sun, since only the latter has an initial capital letter.

To apply a custom translation to a word that might appear with or without initial capitalization, create two entries for both possible occurrences. Include both entries only if the translation is to be applied to both forms of the word.





 Context sensitivity 

The pronunciations of some words are context-sensitive. For example, consider the following example input sentence:

St. Anthony lives on Henry St.

The service's default pronunciation rules correctly synthesize this text as

Saint Anthony lives on Henry Street

However, if you override the default pronunciation rules for the string St. to translate it as saint, the service can no longer pronounce the word based on context. Applying a custom model that includes such a translation causes the service to pronounce the previous input sentence as

Saint Anthony lives on Henry saint

Consider such cases when you develop word/translation pairs.





 Trailing periods 

The service applies a word from a custom model only to those strings in the input text that match the word exactly. A trailing .
Several person records can be maintained on your account for use across multiple subnet registrations. A subnet registration must be associated to a single person record before attempting to inform the registrar of the associated network assignment. If invalid or poorly formatted data is present in the chosen person record, according to the targeted registrar, the registration request is rejected.

Registrar entities maintain different rules for formatting personal data, so it is possible for a person record to be successfully registered with one registrar and to be rejected by another.



 Person record validation rules 

The following sections outline the various validation measures applied to person detail records and their properties when attempting to create or modify subnet registrations.



 First Name 



* First name is required.
* It can contain a maximum of five words.
* First name must not exceed 75 characters.
* The first word must begin with a letter.
* Only the following are valid for this field: a-z A-Z 0-9 '- and space.







 Last Name 



* Last name is required.
* It can contain a maximum of five words.
* Last name must not exceed 75 characters.
* The first word must begin with a letter.
* Only the following are valid for this field: a-z A-Z 0-9 '- and space.







 Address 



* Address is required.
* Address must be 2 - 200 characters.
* Only the following are valid for this field: a-z A-Z 0-9 '/&,.-: and space.







 City 



* City name is required.
* City must be 2 - 50 characters.
* Only the following are valid for this field: a-z A-Z 0-9 .'- and space.







 Postal code 



* Postal code is required for certain locales.
* Postal code cannot exceed 15 characters.
* Only the following are valid for this field: a-z A-Z 0-9 - and space.







 Country 



* Country is required.
* Country code must equal 2 characters, in compliance with [ISO 3166-1](https://www.nro.net/list-of-country-codes-and-rirs-ordered-by-country-code).







 State
Application load balancer limitations 

IBM Cloud® Application Load Balancer for VPC (ALB) has the following known limitations.



*  Two members with the same instance X and same port Y cannot exist at the same time for an ALB. This case is not supported and your traffic might not be routed correctly.
*  The default load balancer quota is 50 per region. To increase the number, you must [create a support case](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case).
nginx.ingress.kubernetes.io/proxy-buffers-number: "4"





 Configuring busy proxy buffer size 

To configure the size of proxy buffers that can be busy, use a [location snippet](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/configuration-snippet). For more info, see the [NGINX docs](http://nginx.org/en/docs/http/ngx_http_proxy_module.htmlproxy_busy_buffers_size).





 Configuring when an ALB can pass a request 

To set when the ALB can pass a request to the next upstream server, use the following Kubernetes Ingress fields.



* Global setting: ibm-k8s-controller-config ConfigMap [fields](http://nginx.org/en/docs/http/ngx_http_proxy_module.htmlproxy_next_upstream):

retry-non-idempotent: true
proxy-next-upstream: error timeout http_500
* Per-resource setting: Ingress resource [annotations](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/custom-timeouts):

nginx.ingress.kubernetes.io/proxy-next-upstream: http_500
nginx.ingress.kubernetes.io/proxy-next-upstream-timeout: 50
nginx.ingress.kubernetes.io/proxy-next-upstream-tries: 3







 Rate limiting 

To limit the request processing rate and number of connections per a defined key for services, use the Ingress resource [annotations for rate limiting](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/rate-limiting).





 Rewriting paths
If you want to check the progress, go to the Activity page. From the navigation pane, click Manage collections, and then click to open the collection.



 I need to crawl lots of sites. What's my limit? 

The service can support a total of 500 crawler connections per Discovery service instance. All of the data sources except Web crawl use one crawler connection each. For Web crawl, one connection is required for every 5 starting URLs. If you add 10 starting URLS, for example, Discovery generates the extra crawler connection that is needed to support the extra 5 URLs. Therefore, the maximum number of starting URLs that you can use depends on the other data collections that are configured in your service instance. You can calculate the limit yourself.

To calculate the starting URL limit, complete the following steps:



1. Calculate the number of other data source collections in the service instance, meaning this project and any other projects in the same Discovery instance.

For example, you might have 2 IBM Cloud Object Store collections in one project and 2 Salesforce collections and 1 SharePoint Online collection in another project. In this example, the total number of other data source collections is 5.
2. Subtract the number of other data source collections from the maximum allowed number of crawler connections, which is 500.

For example, 500 - 5 = 495.
3. Multiply the remainder by 5 to determine the total number of starting URLs that you can use.

For example, 495 x 5 = 2,475.



To use the maximum-allowed number of starting URLs in the example, you would need 25 web crawl collections because each collection allows a maximum of 100 starting URLs to be configured. However, don't configure your instance to use the absolute maximum number allowed. If one or more additional data sources are added subsequently to a project in this service instance, it will impact the number of starting URLs that the instance can crawl successfully.





 Troubleshooting crawler issues 

A 403 Forbidden error is returned
: The website that you want to crawl might block requests from all but a specific set of named entities. If possible, add the crawler to the allowlist for the site.
What do I do if my connection fails? 

Client VPN for VPC requires accurate configuration to complete any connection. Changes to the configuration can disrupt your connection, causing a failure.

  What’s happening 

The VPN connection is failing.

  Why it’s happening 

You changed your configuration, and the connection cannot complete.

  How to fix it 

Follow these steps to resolve this issue:



1.  If you are using client-based authentication, verify that the client certificate information is added to the download client configuration file.

For example, if you update the authentication method from certificate only to both certificate and user ID + passcode authentication, you must download the client profile again and reconfigure the client certificates.
2.  Check the security group configuration and verify that the VPN ports and protocols are added to the inbound and outbound rules.
Submit your account upgrade information again. If the error continues to occur, you can contact [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 Why can't I save my credit card to the account? 

 What’s happening 

An issue occurred that caused the payment process to fail. This error might prompt the following message:

> Your card could not be saved. Please try another card.

 Why it’s happening 

Your card information was incorrect.

 How to fix it 

Use a different credit card to process your transaction.





 Why was my credit card declined? 

 What’s happening 

An issue occurred that caused your credit card to decline. This error might prompt the following message:

> Your payment was declined for invoice number…

 Why it’s happening 

You have a credit card on file and it was declined.

 How to fix it 

Update your credit card information on the [Payments page](https://cloud.ibm.com/billing/payments). Credit card transactions are automatically retried within 24 hours after you update the information.