vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information about these plans, see the [Qiskit Runtime plans](https://cloud.ibm.com/docs/quantum-computing?topic=quantum-computing-plans) topic.



* Lite: Free simulators-only plan to help you get started with Qiskit Runtime. Learn to use Qiskit Runtime by following our examples and tutorials for one of the pre-built programs available for running circuits efficiently.
* Standard: A pay-as-you-go model for accessing IBM Quantum systems and simulators. Build your own programs and leverage all the benefits of Qiskit Runtime by running on real quantum hardware, while maintaining access to all of the systems available to the Lite plan.



Because this is not a free plan, it is important to understand how to best manage your costs. See [Manage the cost](https://cloud.ibm.com/docs/quantum-computing?topic=quantum-computing-cost) for tips to limit your cost, how to set up spending notifications, and more.
2. Complete the required information, then click Create.







 Step 2: Install or update Qiskit packages 

Install or update the following packages in your development environment. They let you create circuits and work with primitive programs with Qiskit Runtime. For detailed instructions, refer to the [Qiskit Getting started topic](https://qiskit.org/documentation/getting_started.html). Periodically check the [Qiskit release notes](https://qiskit.org/documentation/release_notes.html) (or rerun these commands) so that you always have the latest version.

Be sure to run these commands even if you already installed the packages, to ensure that you have the latest versions.

 Installs the latest version of the Qiskit meta-package for circuit creation.
pip install qiskit -U

 Installs the latest version of the Qiskit Runtime package, which is needed to interact with the Qiskit Runtime primitives on IBM Cloud.
pip install qiskit-ibm-runtime -U





 Step 3: Authenticate to the service
If your source documents are supported by Smart Document Understanding (see [Supported document types](https://cloud.ibm.com/docs/discovery?topic=discovery-sdudoctypes)), use document splitting instead of document segmentation. For details, see [document splitting](https://cloud.ibm.com/docs/discovery?topic=discovery-sdusplitting).

You can split your HTML documents into segments based on HTML heading tags. Once split, each segment is a separate document that is enriched and indexed separately. Since queries return these segments as separate documents, document segmentation can be used to:



* Perform aggregations on individual segments of a document. For example, your aggregation would count each time a segment mentions a specific entity, instead of only counting it once for the entire document.
* Perform relevancy training on segments instead of documents, which improves result reranking.



Documents can be split based on the following HTML tags: h1h2h3h4h5 and h6.

Considerations:



* In the Lite plan, the number of segments per document is limited to 250. Any document content remaining after 249 segments are stored within segment 250. In the Advanced plan, the number of segments per document is limited to 1,000. Any document content remaining after 999 segments are stored within segment 1,000. Segmentation limits are dependent on your plan. For more information, see [Discovery pricing plans](https://cloud.ibm.com/docs/discovery?topic=discovery-discovery-pricing-plans).
* Each segment counts towards the document limit of your plan. Discovery indexes segments until the plan limit is reached. See [Discovery pricing plans](https://cloud.ibm.com/docs/discovery?topic=discovery-discovery-pricing-plans) for document limits.
* You can not use CSS selectors to extract fields (see [Using CSS selectors to extract fields](https://cloud.ibm.com/docs/discovery?topic=discovery-configserviceusing-css)) when using document segmentation.
* Documents are segmented each time the specified HTML tag is detected.
For more information about the plan description, see the [service catalog](https://cloud.ibm.com/catalog/services/continuous-delivery). If any of the plan limitations are exceeded in a billing period, the service suspends. For example, Classic Delivery Pipeline jobs (or Tekton pipeline runs) do not run for the remainder of the billing period.

Upgrading to the Professional plan will remove these limitations and reactivate the service.





 How can you change to a different service plan? 

You can upgrade from the Continuous Delivery Lite service plan to the Professional plan.



1. From the console, click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/icons/icon_hamburger.svg) > Resource list to view your list of resources.
2. Click the Continuous Delivery service that you want to upgrade.
3. Click Plan in the Continuous Delivery service instance dashboard.
4. In the Change pricing plan section, select Professional to upgrade to the Continuous Delivery Professional plan, and click Save.
5. After you change your plan, you must restage your app. Go to your resource list to find the app that the service is bound to. Click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/icons/icon_hamburger.svg)> Resource list. In the app menu, select Restart App.







 Changing a plan through the CLI 

As an alternative to the console, you can change the Continuous Delivery service's pricing plan by using the IBM Cloud command-line interface (CLI).



1. Check whether the service is enabled with the resource controller.

ibmcloud catalog service continuous-delivery

If the service is enabled with the resource controller (RC), it lists RC Compatible true.
If you are having trouble logging in to a service instance or see messages about tokens, such as unable to fetch access token or 400 bad request - header or cookie too large, it might mean that you need to clear your browser cache. Open a private browser window, and then try again.



* If accessing the page by using a private browsing window fixes the issue, then consider always using a private window or clear the cache of your browser. You can typically find an option for clearing the cache or deleting cookies in the browser's privacy and security settings.
* If accessing the page by using a private browsing window doesn't fix the issue, then try deleting the API key for the instance and creating a new one.







 I'm being asked to log in repeatedly 

If you keep getting messages, such as you are getting redirected to login, it might be due to one of the following things:



* The Lite plan you were using has expired. Lite plans expire if they are not used within a 30-day span. To begin again, log in to IBM Cloud and create a new service instance of Watson Assistant.
* An instance is locked when you exceed the plan limits for the month. To log in successfully, wait until the start of the next month when the plan limit totals are reset.







 I'm getting a 401 response 

The 401 response code is returned for many reasons, including:



* You exceeded the API call limit for your plan for this month. For example, for Lite plans, the monthly limit for API calls 10,000 messages per month. If you reach your limit for the month, but the logs show that you have made fewer calls than the limit, remember that the Lite plan stores log information for 7 days only. The 401 response will go away as soon as the next billing cycle begins, which is the first day of the calendar month.
* You are trying to use an instance-level API key that you created in one data center location to connect to a service instance that is hosted from another location. You must create an API key in the same data center location where your service instance is hosted.







 Getting Unable to fetch access token for account message 

The full message is, Assistants could not be loaded at this time.
If you reach your limit for the month, but the logs show that you have made fewer calls than the limit, remember that the Lite plan stores log information for 7 days only. The 401 response will go away as soon as the next billing cycle begins, which is the first day of the calendar month.
* You are trying to use an instance-level API key that you created in one data center location to connect to a service instance that is hosted from another location. You must create an API key in the same data center location where your service instance is hosted.



* Getting Unable to fetch access token for account message

The full message is, Assistants could not be loaded at this time. Unable to fetch access token for account.

This message is displayed for a few reasons:



* Your IBM Cloud® refresh tokens might have expired. Log out and then log back in to IBM Cloud to generate fresh tokens.
* Make sure that the IBM ID that you logged in with has access to this service instance. To confirm, you can go to the [IBM Cloud resources list](https://cloud.ibm.com/resources), and then log in with the same IBM ID. You should see this service instance listed as one of your available services.



* Getting Authentication Required or Sign in message

You are being asked for credentials to access a Watson Assistant service instance that you have been able to access without trouble in the past. You might see, Authentication Required: {service-url} is requesting your username and password. or just a Sign in dialog box with fields for a username and password.

This message can be displayed for service instances that were migrated from Cloud Foundry, but for which access roles were not subsequently updated. After the migration, the service instance owner must update the user permissions to ensure that anyone who needs access to the instance is assigned to the appropriate Platform and Service access roles.

To regain access to the service instance, ask the service instance owner to review your access permissions. Ask to be given at least a service access role of Writer.

After your access roles are fixed, be sure to use the correct web address, the URL of the migrated service instance, to open it.
* I don’t see the Analytics page
Update to version string : The version string for all API calls changed to 2018-12-03 from 2018-10-15. The Discovery tooling does not yet use this API version (it currently uses 2018-08-01), so queries written using the Discovery tooling does not return a confidence score for untrained collections.





 8 November 2018 

New Tokyo location now available : Discovery launched in the Tokyo location 8 November 2018. Premium and Dedicated environments are not currently available in Tokyo.





 30 October 2018 

New IAM support in all regions : Discovery now supports token-based Identity and Access Management (IAM) authentication in all regions. IAM uses access tokens rather than service credentials for authentication with a service. For more information about using IAM tokens with existing and new applications, see the [17May2018](https://cloud.ibm.com/docs/discovery?topic=discovery-release-notesdiscovery-17may2018) release update.





 25 October 2018 

Update to Element Classification enrichment schema : The schema for the [Element Classification](https://cloud.ibm.com/docs/discovery?topic=discovery-element-classification) enrichment changed. If you wish to use the updated schema, you must ingest your documents with the API, using the version date of 2018-10-15 or later. The Discovery tooling does not yet use this API version (it currently uses 2018-08-01), so documents ingested, using the Discovery tooling, are enriched with the original schema.





 24 October 2018 

New highlights to replace queries display from JSON field : IBM Watson™ Discovery News queries display approximately 50 words from each article in the text JSON field. These words are now extracted from the highlights, rather than simply displaying the first 50 words of the article. See [highlight](https://cloud.ibm.com/docs/discovery?topic=discovery-query-parametershighlight) for an explanation of highlights. Highlights do not need to be explicitly included in your query to enable this behavior.





 25 September 2018 

New Continuous Relevancy Training feature : Released Continuous Relevancy Training, which uses interactions from users to learn how to surface the most relevant results.
Select the [location](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-regions) where you plan to provision the instance.
6. Select a resource group.

By default, the default resource group is set.

Note: If you are not able to select a resource group, check that you have editing permissions on the resource group where you want to provision the instance.
7. Select the Lite service plan.

By default, the lite plan is set.

For more information about other service plans, see [Pricing plans](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-service_plans).
8. Click Create.



After you provision an instance, the Logging dashboard opens.

Next, configure a log source by adding a logging agent. This agent is responsible for collecting and forwarding logs to your instance.





 Provisioning an instance through the catalog 

To provision an instance of IBM Log Analysis through the IBM Cloud catalog, complete the following steps:



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).

After you log in, the IBM Cloud UI opens.
2. Click Catalog. The list of the services that are available in IBM Cloud opens.
3. To filter the list of services that is displayed, select the Logging and Monitoring category.
4. Click the IBM Log Analysis tile.
5. Select the [location](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-regions) where you plan to provision the instance.
6. Enter a name for the service instance.
7. Select a resource group.

By default, the Default resource group is set.

Note: If you are not able to select a resource group, check that you have editing permissions on the resource group where you want to provision the instance.
8. Select the Lite service plan.

By default, the lite plan is set.
The service can be provisioned from [its catalog page](https://cloud.ibm.com/catalog/ibm-cloud-activity-tracker) or from an existing [Observability Dashboard](https://cloud.ibm.com/observe/activitytracker).

The Activity Tracker service has a lite plan that is free to use, but it only offers streaming events. To take advantage of the tagging, export, retention, and other features, you need to use one of the [paid plans](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-service_plan).



 Using the Activity Tracker 

You can access Activity Tracker through the Observability tab of your deployment's Manage page. The Manage Activity Tracker button links to the main list of all Activity Tracker instances in your IBM Cloud account. Select the instance where you set your database logs to be forwarded. Click View Activity Tracker to view the events.

Once event activity is being forwarded to the service, each event can be expanded to a detailed view by clicking the arrow to the left of the timestamp.

When reviewing Activity Tracker logs, you see denies that include the dry_run tag. These denies are marked with a true or false value.



* Events with dry_run: false indicate an attempt to run an action.
* Events with dry_run: true indicate an attempt to determine support for an action without triggering that action to occur. Such dry_run attempts can occur as the service instance management console determines the features to which a logged in user has access.



The Activity Tracker service offers [searching](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-view_eventsview_events_step2), [filtering](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-view_eventsview_events_step3), and [export](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-export) of events so you can customize retention for your use-case.
Migration FAQ 

Find answers to questions that are commonly asked about migrating from Discovery v1 to v2.

Do the two versions have all the same features?
:   There are many feature differences between the two versions. For a full feature comparison, see [Getting the most from Discovery](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-version-choose).

How do I know which version I'm using now?
:   When you open the product user interface in v2, the following page is displayed:

Zoom

![Shows the main My Projects page with a single Sample Project tile.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/gs-home-page.png)

Figure 1. Home page from the Sample Project

How long will the migration take?
:   The time you need to set aside for the migration differs based on the amount of data you want to retain in your existing v1 service instance.

Do I need to update my existing applications for them to work with v2?
:   Yes. You will need to edit any existing applications to account for changes that are introduced with Discovery v2. For more information, see the [API version comparison](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-migrate-to-v2-api).

To get started, see [Migrating to Discovery v2](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-migrate-to-v2).
Go to the [Discovery resource](https://cloud.ibm.com/catalog/services/watson-discovery) page in the IBM Cloud catalog and create a Plus plan service instance.



If you decide to stop using the Plus plan and don't want to pay for it, delete the Plus plan service instance before the 30-day trial period ends.







 Step 1: Create an assistant 

For this tutorial, you will create an assistant with a single action. First, you must create a Watson Assistant service instance.

Both Lite and Trial plan Watson Assistant service instances are available at no cost. You will create a Trial plan because a Plus or higher plan is required to add a search skill to an assistant and the Trial plan includes all Plus plan features. The Lite plan does not.



1. Create a Trial plan Watson Assistant service instance in the same data location where the Discovery service instance is hosted, such as Dallas.
2. From the Watson Assistant plan service page in IBM Cloud, click Launch Watson Assistant.

The Watson Assistant product user interface is displayed where you can create your first assistant.
3. Add FRED research as the assistant name, and then click Next.

Zoom

![Shows the Watson Assistant welcome page](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/tut-convo-assis-intro-2.png)

Figure 1. Watson Assistant welcome page
4. Fill out the fields to share information about you and your assistant, and then click Next.

In the Which statement describes your needs best field, choose I'm using Watson Assistant to complete a course or certification..

Zoom

!
* What does the IN_PROGRESS status mean when I apply a subscription code?

When you apply a subscription code to a Pay-As-You-Go account, the status of the subscription might be IN_PROGRESS. This status indicates that your account must be reviewed to complete your order. When you see this status, contact the IBM Cloud Sales representative who helped you with the order.
* Can I pay the total spending commitment up-front or quarterly?

Yes! By default, you're billed monthly for your subscriptions. If you'd like to pay up-front or quarterly, contact [IBM Cloud Sales](https://www.ibm.com/cloud?contactmodule).
* Can I spend more or less than my monthly commitment?

Yes, what you spend monthly is up to you! You can spend any amount of the total commitment each month.
* What happens if I spend my entire subscription amount before my term ends?

You're required to continue paying your monthly charges until the end of your term. You're charged the non-discounted rate for any usage that goes over your total subscription amount. To avoid overage charges, contact [IBM Cloud Sales](https://www.ibm.com/cloud?contactmodule) to sign up for a new subscription.
* Is there a monthly minimum amount required for Subscription accounts?

Yes, your subscription must have a combined minimum spending and term commitment of $100.00 USD each month for 12 months.
* Can I cancel my Subscription account before the end of my term commitment?

A subscription is a contract between you and IBM that commits you to use IBM Cloud for a specific term and spending amount. You can request to cancel your subscription before the end of the term, but whether the subscription can be canceled is at the discretion of IBM. Any remaining credit on your subscription might be forfeited. For more information, contact [Support](https://cloud.ibm.com/unifiedsupport/supportcenter). Make sure that you provide details about why you need to cancel your subscription.

To close a Pay-As-You-Go account or a Lite account, see [Can I cancel my account?]
Improved SharePoint Online connector
: The Microsoft SharePoint Online data source connector now accepts any valid Azure Active Directory user ID syntax; the format of the user ID doesn't need to match the <admin_user>@.onmicrosoft.com syntax. For more information, see [Microsoft SharePoint Online](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-sharepoint-online-cloud).





 16 July 2021 

New beta dynamic website web crawl
: The Web crawler can now crawl dynamic websites that use JavaScript to render content. If you enable this beta feature, the time it takes to crawl the site increases. For more information, see [Web crawl](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-web-cloud).





 23 June 2021 

New Plus plan
: Use the new Plus plan and its associated 30-day free trial to explore new features and a simpler way to build that is available with the latest version of the product. Currently, the Plus plan is available from the Dallas location. For more information, see [Getting the most from Discovery](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-version-choose).

Change to Lite and Advanced plans
: Lite and Advanced plans are no longer offered. You cannot create new service instances that use the Lite or Advanced plan types in the Dallas location. Any existing Lite and Advanced plans continue to function properly and continue to be supported. You can upgrade from a Lite plan to an Advanced plan.





 Endpoint deprecation reminder 

Change to Discovery API endpoint
: As part of work done to fully support Identity and Access Management (IAM) authentication, the endpoint that you use to access your Discovery service programmatically is changing. The old endpoint URLs are deprecated and will be retired on 26 May 2021. Update your API calls to use the new URLs.

The pattern for the endpoint URL changed from gateway-{location}.watsonplatform.net/discovery/api/ to api.