vania-janet/multiturn-rag-retrieval-data huggingface dataset:
This documentation is for the classic Watson Assistant experience. To see the documentation for the new Watson Assistant, please go [here](https://cloud.ibm.com/docs/watson-assistant).



 Integrating with Slack 

Slack is a cloud-based messaging application that helps people collaborate with one another.

After you configure a dialog skill and add it to an assistant, you can integrate the assistant with Slack.

When integrated, depending on the events that you configure the assistant to support, your assistant can respond to questions that are asked in direct messages or in channels where the assistant is directly mentioned.



 Adding the Slack integration 



1. From the Assistants page, click to open the assistant tile that you want to deploy.
2. From the Integrations section, click Add integration.
3. Click Slack.
4. You need to have a Slack app to connect to.

If you don’t have a Slack app, create one now. See [Starting with Slack apps](https://api.slack.com/start).
5. Go to the [Your Apps](https://api.slack.com/apps) page on the Slack website, and then click the app you want to use.

Open the Slack app in a new browser tab, so you can easily switch back and forth between the Slack app settings page and Watson Assistant Slack integration configuration page.
6. From the settings page for your Slack app, open the App Home page.
7. Add access scopes for your Slack app.

The button label might be Review Scopes to Add or Update scopes depending on whether you are creating a new app or editing an app that you created before February 2020.

The method for Slack access changed. For more information about it, read the [Slack blog post](https://medium.com/slack-developer-blog/more-precision-less-restrictions-a3550006f9c3) about it.
8. Assign bot token scopes to your Slack app. At a minimum, apply the following scopes:



* app_mentions:read
* chat:write
* im:history
* im:read
This release of Watson Assistant for IBM Cloud Pak® for Data includes various fixes and features.

Algorithm version 01-Jun-2022 uses enhanced intent detection by default
: The algorithm version Latest (01-Jun-2022) now uses enhanced intent detection by default. Before this change, some skills that did not include a specific algorithm version selection inadvertently used Previous (01-Jan-2022). You can notice small changes in intent detection behavior when changes are made to an assistant that previously didn't have enhanced intent detection enabled. For more information, see [Algorithm version and training](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-algorithm-version).

Test the Beta algorithm version now to prepare for release 4.7.0
: The Beta algorithm version in release 4.6.5 includes a new irrelevance detection implementation to improve off-topic detection accuracy.

Improvements include:



* Relevant user inputs are expected to get higher confidence, so they are less likely to be considered irrelevant or require clarification
* Irrelevance detection is improved in the presence of direct entity references
* Irrelevance detection is more stable across small changes to input
* Intent detection is more stable regarding occurrence of numerics, such as postal codes
* For German-language assistants, intent detection is more robust in the presence of umlauts



In the forthcoming 4.7.0 release, it is planned that this Beta version will become the Latest version, replacing the current Latest (01 Jun 2022) version. You can test the Beta version in 4.6.5 now to prepare.

For more information, see [Algorithm version and training](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-algorithm-version).





 23 February 2023 

IBM Watson® Assistant Cartridge for IBM Cloud Pak® for Data Version 4.6.3 is available
: Watson Assistant for IBM Cloud Pak® for Data 4.6.3 is compatible with IBM Cloud Pak® for Data Version 4.6.
oc patch wa ${INSTANCE_NAME} --type='json' --patch='{"op": "add", "path": "/appConfigOverrides/clu", "value":{"master":{"autoscaling":{"enabled":false}}}}] ! ! ! '
2. Wait until the information propagates into the Watson Assistant operator:
sleep 600
3. Run the following command to remove HPA for the master microservice
oc delete hpa ${INSTANCE_NAME}-master
4. Wait for about 30 seconds:
sleep 30
5. Finally, scale down the master microservice to the number of replicas that you want. In the following example, the master microservice is scaled down to two replicas:
oc scale deploy ${INSTANCE_NAME}-master --replicas=2
<-- </ol> --><-- </section "id="section-troubleshoot-150-disable-hpa" "> --><-- <section "id="section-watson-assistant-150-patch-1" "> --> Watson Assistant 1.5.0 patch 1 Watson Assistant 1.5.0 patch 1]Watson Assistant 1_.5_.0 patch 1] ! ! is available for installations of version 1.5.0.<-- </section "id="section-watson-assistant-150-patch-1" "> --><-- <section "id="section-resizing-the-redis-statefulset-memory-and-cpu-values-after-applying-patch-1-for-watson-assistant-150" "> --> Resizing the Redis statefulset memory and cpu values after applying patch 1 for Watson Assistant 1.5.0 Watson Assistant uses Redis to store web session-related data. Here are steps to resize Redis statefulset memory and cpu values after applying Watson Assistant 1.5.0 patch 1]Watson Assistant 1_.5_.0 patch 1] !
The data that is stored by a variable is characterized by the type of data that it contains, such as text, a numeric value, a date, or even a list of multiple values. The operations that you can perform with a variable vary depending on its data type.



 Action variables and session variables 

Watson Assistant supports two categories of variables:



* Action variables: When a step collects information from the customer, the customer response is automatically stored in an action variable. You can think of action variables as short-term memory: they persist only during the current action.

The name of an action variable is always the name of the step that defines the customer response. (You cannot change the name of an action variable.) For example, suppose you define a step that asks "When were you born?" and accepts a date value as a response. The customer response is automatically stored as an action variable called When were you born?, which you can then access from any subsequent step in the same action.
* Session variables: A value that is not necessarily tied to a particular action can be stored as a session variable. Session variables are long-term memory: they persist throughout the user's interaction with the assistant, and your assistant can reference them from any action.

You can create a session variable to store the value from an action variable, if you want to keep the value available for other actions to use. You can also define a session variable based on another session variable, or by using a value defined in an expression. In addition to variables you create, Watson Assistant provides a set of built-in session variables for global values like the current time and date.

Session variables can help you to modularize your assistant because you can write a single action that collects information that is needed in multiple places. For example, you might have a greeting action that collects basic information about the customer and stores the responses in session variables, which any action can then access.

A session variable that you create persists only during a single session. At the end of the session, the variable's value is cleared. How long a session lasts depends upon how your customers access your assistant, and how your assistant is configured.





 Creating a session variable 

To add a session variable that can be accessed by any action:



1.
: Watson Assistant for IBM Cloud Pak® for Data version 1.4.1 is compatible with IBM Cloud Pak® for Data version 2.5.

New backup and restore
: A new backup and restore script is available. See [Backing up and restoring data](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-backup).

Webhooks now generally available
: The Webhooks feature is now generally available. See [Making a programmatic call from dialog](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-webhooks).

Bug fixes
: Multiple bug fixes were made.

Features not included
: This release does not include the following features, which are available for cloud instances at the time of this release:



* There are no metrics or analytics capabilities. Therefore, the Analytics page is not included in the product user interface.
* There are no deployment connectors or built-in integrations available. You must build a custom client application that can host the assistant. As a result, the Integrations page is not included in the product user interface.
* The @sys-person and @sys-location system entities are not supported and the updated numeric system entities are not available.
* There is no search function in the product.
* You cannot use the Activity Tracker service to track user actions.
* Autocorrection, intent recommendations, and the new irrelevance detection model are not supported.
* The product tour that is available to some first-time users of the cloud-based product is not available.







 27 November 2019 

IBM Watson® Assistant for IBM Cloud Pak® for Data version 1.4 is available
: Watson Assistant for IBM Cloud Pak® for Data version 1.4 is compatible with IBM Cloud Pak® for Data version 2.5.

Czech language not automatically enabled
: The Czech language is not enabled automatically anymore.

Assistants and Skills navigation menu update
: The main menu options of Assistants and Skills have moved from being displayed at the top of the page to being shown as icons in a new navigation pane.



* !
Updating endpoint URLs from watsonplatform.net 

Watson API endpoint URLs at watsonplatform.net are changing and will not work after they are retired. Update your calls to use the newer endpoint URLs.

The watsonplatform.net endpoint URLs were retired on 26 May 2021. Update your API calls to use new URLs.

As each Watson service announced in December 2019, the pattern for the new endpoint URLs is api.{location}.{offering}.watson.cloud.ibm.com. For example, with Watson Assistant services that are hosted in Washington DC, the message endpoint changes from https://gateway-wdc.watsonplatform.net/assistant/api/v1/workspaces/{workspace_id}/message to https://api.us-east.assistant.watson.cloud.ibm.com/instances/{instance_id}/v1/workspaces/{workspace_id}/message. The domain, location, and offering identifier are different in the new endpoint.

When you call a Watson API, use the new base URL that corresponds to your Watson offering and to the location where your service instance is hosted.



 Finding and updating the endpoint URL 

You can find the URL for your service instance with the service credentials. You can also update the endpoint URL and API key in the same place.



1. Click the name of the service in the [Resource list](https://cloud.ibm.com/resources?groups=resource-instance).
2. If you see a URL with the domain watsonplatform.net in the credentials, update the credentials:



1. Click the Service credentials tab, and then click New credential.
2. Expand the new credentials and look for the url. The pattern is api.{location}.{offering}.watson.cloud.ibm.com.
3. Look for the apikey in the new credentials.



3. Delete the older credentials by clicking the Delete icon !
The Complete tab bar chart is organized by conversations either completed by the assistant or completed by a planned connect to agent response.

As you click on each tab, a table below the chart shows the list of either incomplete or complete requests. To explore individual requests in detail, you can click on each one. A panel opens showing the full back and forth between your customer and the assistant, including step interactions. The panel also provides a summary of how many requests there were, how many were recognized, whether search was initiated, and the duration of the conversation.

![Request detail](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/analytics-completion-side-panel.png)



 Editing an action 

After you decide on changes you want to make to improve the action, click the edit icon in the header for the single action, which opens your action for further work on its steps.

![Edit action](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/analytics-completion-edit-action.png)
The app fails to deploy with the message: API/0App instance exited ... payload: {... "reason"=>"CRASHED", "exit_status"=>-1, ...}.

 Why it’s happening 

If you receive a similar message when you push your ASP.net app, it is most likely because your app exceeds either the memory or disk quota limits. Increase the quotas for memory or disk space for your app.

 What’s happening 

The app fails to deploy with the message: Failed to compress droplet: signal: broken pipe or No space left on device. How can I fix this?

 Why it’s happening 

Projects pushed from source code that contains a large number of NuGet package dependencies can sometimes cause this error when the NuGet package cache is enabled. Set the CACHE_NUGET_PACKAGES environment variable to false to disable the cache.



 Helpful links 



* [NuGet](https://docs.microsoft.com/en-us/nuget/consume-packages/overview-and-workflow)
* [ASP.NET Core Overview](http://docs.asp.net/en/latest/conceptual-overview/aspnet.html)









 PHP 



 NOTICE messages from the PHP buildpack 

You might see messages that contain NOTICE from the logs. You can stop the logging of these messages by changing the logging level.

 What’s happening 

When you push an app to IBM Cloud by using a PHP buildpack, you might see messages that contain NOTICE:

* 2015-01-26T15:00:59.70+0100 [App/0] ERR [26-Jan-2015 14:00:59] NOTICE: [pool www] 'user' directive is ignored when FPM is not running as root
* 2015-01-26T15:01:00.63+0100 [App/0] ERR [26-Jan-2015 14:00:59] NOTICE: [pool www] 'user' directive is ignored when FPM is not running as root
How do I know when to attach capacity to the Satellite location control plane? 

When you list locations, such as with the ibmcloud sat location ls command or in the [Satellite console](https://cloud.ibm.com/satellite/locations), the location enters an Action required health state. You see warning messages similar to the following example.

Hosts in the location control plane are running out of disk space.

Hosts in the location control plane have critical CPU or memory usage issues.

The location control plane is running at max capacity and cannot support any more workloads.

After you determine the size of your location, [add hosts to the location control plane](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hosts).





 How do I scale up my Satellite location control plane to be highly available? 

See [Highly available control plane worker setup](https://cloud.ibm.com/docs/satellite?topic=satellite-hasatellite-ha-setup). Make sure to attach hosts to the control plane location in each zone, in multiples of three. For example, you might have 6 hosts that are assigned to your control plane location that is managed from the IBM Cloud wdc region, with 2 hosts each zone (us-east-1, us-east-2, and us-east-3).

To scale up your control plane, you can follow the same steps to [Set up the Satellite location control plane](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-control-plane).





 How many Red Hat OpenShift on IBM Cloud clusters can I run before I need to attach capacity to the location control plane? 

The number of clusters depends on the size of your clusters and the size of the hosts that you use for the Satellite location control plane. You must scale up the control plane hosts in multiples of 3, such as 6, 9, or 12.

The following tables provide examples of the number of hosts that the control plane must have to run the masters for various combinations of clusters and worker nodes, for informational purposes only.
* Where do I specify the Slack channel name in the Slack Destination configuration?

Event Notifications supports the Slack destination using Slack's “Incoming Webhook” feature. An incoming webhook is linked directly to a Slack channel. Hence, there is no need to separately specify the Slack channel.
* Is it possible to customize the message that is generated from IBM Cloud services ((IBM Cloud sources)?

You cannot customize messages that are generated from IBM Cloud services ((IBM Cloud sources). These notifications are generated by the respective IBM Cloud service such as Secrets Manager, and Security and Compliance Center. The message content cannot be modified by the end user before it is sent out to a destination.
* Why do I get a 422 error response for the Send Notifications API call?

Event Notifications service is unable to process your request. This is usually seen when there is no condition or filter associated with the topic to which the notification is sent. Check your topic and verify that it is connected to the correct source, with the intended conditions.
* Why my email notifications sent didn’t reach customers even though in the logs I can see successfully sent notifications?

This may be due to your Event Notifications instance has a subscription created for the smtp_ibm destination and has no email ID added as a recipient to the list for the subscription.

Make sure your Event Notifications instance has a subscription created for the smtp_ibm destination and has at least one email ID added as a recipient to the list for the subscription.
* Is it possible to send notifications to more than one destination using Event Notifications?

Yes. You can send notifications to more than one destination.



IBM Cloud Email Delivery for Classic



* FAQs

 FAQs 



As of 28 October 2015, IBM Cloud® no longer allows outbound connections through TCP port 25 (SMTP) on new accounts.





By default, the standard SMTP TCP port 25 is blocked due to the large amount of abuse that is targeted at this port. IBM Cloud® offers a trusted third-party email relay service from SendGrid if you need to send outbound email from their domains or applications.





If you need send email from your servers, you need to use a smart host outside of IBM Cloud®.
Workshops and events 

Enroll in workshops and events to learn how to build products to sell on IBM Cloud®.

To view workshops and events, you need the viewer role on the Partner Center account management service. For more information, see [Assigning access to account management services](https://cloud.ibm.com/docs/account?topic=account-account-servicesaccount-management-actions-roles).



  Recommendations 

The list is generated based on your profile and preferences. You can filter the list by content type.



*  To update your profile, see your partner profile.
*  To update your preferences, see your partner profile.







  Upcoming workshops and events 

Enroll in workshops and events to learn how to build products for IBM Cloud®. You can filter the list by content type.
A common pattern is to commit the offset of the latest processed message based on a periodic timer. This pattern means that every message is processed at least once, but the committed offset never overtakes the progress of messages that are actively being processed. The frequency of the periodic timer controls the number of messages that can be reprocessed following a consumer failure. Messages are retrieved again from the last saved committed offset when the application restarts or when the group rebalances.

The committed offset is the offset of the messages from which processing is resumed. This is usually the offset of the most recently processed message plus one.





 Consumer lag 

The consumer lag for a partition is the difference between the offset of the most recently published message and the consumer's committed offset. Although it's usual to have natural variations in the produce and consume rates, the consume rate is not to be slower than the produce rate for an extended period.

If you observe that a consumer is processing messages successfully but occasionally appears to jump over a group of messages, it can be a sign that the consumer is not able to keep up. For topics that are not using log compaction, the amount of log space is managed by periodically deleting old log segments. If a consumer fell so far behind that it is consuming messages in a log segment that is deleted, it will suddenly jump forwards to the start of the next log segment. If it is important that the consumer processes all of the messages, this behavior indicates message loss from the point of view of this consumer.

You can use the kafka-consumer-groups tool to see the consumer lag. You can also use the consumer API and the consumer metrics for the same purpose.







 Controlling the speed of message consumption 

If you have problems with message handling that is caused by message flooding, you can set a consumer option to control the speed of message consumption. Use fetch.max.bytes and max.poll.records to control how much data a call to poll() can return.





 Handling consumer rebalancing 

When consumers are added to or removed from a group, a group rebalance takes place, and consumers are not able to consume messages. This results in all the consumers in a consumer group to be unavailable for a short period.
Why can’t I connect to my IBM Cloud® Messages for RabbitMQ deployment? 

If you encounter errors when connecting to your IBM Cloud® Messages for RabbitMQ deployment, review these common causes and solutions.

  What’s happening 

You receive an error message or fail to connect to a Messages for RabbitMQ deployment. When reviewing application logs, you might see errors that mention intermittent connection timeouts or unable to connect.

  How to fix it 

Review the following information to troubleshoot and resolve common connectivity problems:



*  An unsecured connection is a common cause of connectivity errors. All Messages for RabbitMQ connections use TLS/SSL encryption. Messages for RabbitMQ rejects unsecured connections. To avoid errors, make sure you configured a secure connection. For more information, see [Getting Started](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-getting-started).
*  If you are using a private endpoint, make sure that you specify connection strings that contain the [Private Endpoint](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=cloud-databases-service-endpointscredentials-for-private-endpoints) and that you followed the steps in [Connecting through Private Endpoints](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=cloud-databases-service-endpointsprivate-endpoint-connections).
*  If your application log captures a short connection interruption, that behavior is expected as a normal part of operations for this managed service. Design your applications to retry connections when errors are caused by a temporary loss in connectivity to your deployment or to IBM Cloud.
*  If retrying your connection hasn't worked, reestablish your connection. If a connection has closed, retrying will have no effect.
*  If you experience several minutes of connection interruption, check the Cloud Status for the service. For more information, see [Application-level High-Availability](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-high-availabilityhigh-availability-for-your-application).