vania-janet/multiturn-rag-retrieval-data huggingface dataset:
CLI version 1.43.5 released
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).

Updated versions for buildpacks
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).





 10 May 2023 

Terraform support for Code Engine is generally available.
: See [Setting up Terraform for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-terraform-setup-ce).





 05 May 2023 

Updated versions for buildpacks
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).







 April 2023 

Review the release notes for April 2023.



 27 April 2023 

CLI version 1.43.4 released
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).

Updated versions for buildpacks
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).





 26 April 2023 

Added support for Code Engine project-wide settings
: Added support for configuring project-wide settings for service binding operations and access to IBM Cloud Container Registry in the console. See [Configuring project-wide settings](https://cloud.ibm.com/docs/codeengine?topic=codeengine-project-integrations).

Updated support for TLS secrets
: Updated support for creating TLS secrets in the console to also permit the upload of a certificate chain and its private key from a file.
For more information, see [deprecated feature warnings](https://docs.couchdb.org/en/stable/whatsnew/3.0.htmldeprecated-feature-warnings).

As a result, these functions are no longer supported for IBM Cloudant. They do not appear in IBM Cloudant documentation, and while the APIs currently remain in service, their use is not recommended. The IBM Cloudant Support team no longer supports them.

Information on alternatives to these functions can be found in the IBM Cloudant blog at [deprecated functions](https://blog.cloudant.com/2022/08/16/Show-list-rewrite-udpate-functions-deprecated.html).
[Snapshots](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-snapshots)





 April 2022 

Phased rollout support for feature flags is available for Lite and Enterprise plan.

Upgrade the server SDKs to version 0.3.0 or higher version for the phased rollout feature.





 January 2022 

IBM Cloud App Configuration is now available in Washington DC region.





 September 2021 

JSON and YAML file support to String type [feature flags](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-feature-flags) and [properties](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-properties).





 Aug 2021 

In-memory based cache support for Node.js and Go SDK





 July 2021 

[Environment-based access control](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-service-access-level-management)





 June 2021 

[Import](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-cli-plugin-app-configuration-cliac-ibmcloud-ac-import) and [export](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-cli-plugin-app-configuration-cliac-ibmcloud-ac-export) of configuration data





 May 2021 

IBM Cloud App Configuration is made generally available (GA).





 April 2021 

[Support for Environments](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-environments)
Service Level Agreement (SLA) for Event Streams availability 



 Standard plan 

The Event Streams Standard Plan provides a highly available architecture by multi-zone region deployment. In a multi-zone location, the Event Streams service is distributed across three availability zones, which means that the cluster is resilient to the failure of a single zone or any component within that zone.

The Event Streams service is provided with availability of 99.99% on the Standard Plan. For more information about the SLA for high availability services in IBM Cloud®, see [Service Level Agreements for IBM Cloud (Public Cloud)](https://www.ibm.com/support/customer/csol/terms?id=i126-9268&lc=endetail-document).





 Enterprise plan 

The Event Streams Enterprise Plan provides a highly available architecture by multi-zone region deployment. In a multi-zone location, the Event Streams service is distributed across three availability zones, which means that the cluster is resilient to the failure of a single zone or any component within that zone.

In a multi-zone region deployment the Event Streams service is provided with availability of 99.99% on the Enterprise plan. For more information about the SLA for high availability services in IBM Cloud, see [Service Level Agreements for IBM Cloud (Public Cloud)](https://www.ibm.com/support/customer/csol/terms?id=i126-9268&lc=endetail-document).

When the Event Streams service is run in a non-highly available configuration, such as [single zone locations](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-slasla_szr), the availability is 99.9%. For more information about the SLA for non-highly availabile services in IBM Cloud, see [Service Level Agreements for IBM Cloud (Public Cloud)](https://www.ibm.com/support/customer/csol/terms?id=i126-9268&lc=endetail-document).





 Satellite plan 

The Event Streams Satellite plan provides a highly available architecture by multi-zone region deployment.
Query (_find endpoint) improved
: IBM Cloudant Query now uses a new method to select an index. Learn more about [IBM Cloudant Query index selection](https://www.ibm.com/support/pages/improving-cloudant-query-index-selection).

Index validation
: The logic for determining whether a specific index is valid for a query that changed, addressing a bug that might lead to incorrect results.

Text indexes
: Queries that use text indexes no longer fail when $exists: false is used.

Partial indexes
: Partial indexes are now supported for both JSON and text indexes. For more information, see [Creating a partial index](https://cloud.ibm.com/apidocs/cloudantpostindex) to learn about the partial_filter_selector parameter.

Execution statistics
: Execution statistics about a query can now be generated. These statistics are enabled by using the execution_stats=true parameter. For more information, see [querying an index by using selector syntax](https://cloud.ibm.com/apidocs/cloudantpostfind) to learn more about execution_stats=true parameter.

Pagination
: [Pagination](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-pagination-and-bookmarks) is supported by using the bookmark field. Bookmarks are enabled for all index types.

use_index field invalid
: _find now falls back to any valid index if the value specified in the use_index field is invalid for the current query. When find falls back, the warning field is populated in the query response.





 9 October 2017 

Error handling
: If you rely on 500 replies for your application, you might have issues. To fix the problem, update your application to rely on 400 responses.
: If you don't take care of reduce overflow errors as part of a row in the response body, issues occur. To fix this problem, change the application to handle the errors from view requests.







 August 2017 



 17 August 2017 

The following changes were made in build 6365:

New!
If you suspect that a problem lies with an officially supported client library, then try to construct a small, self-contained code example that demonstrates the issue. In this self-contained code example, use as few other dependencies as possible. If you’re using Java™, it is helpful to us if you can use a minimal [test harness](https://github.com/mikerhodes/java-cloudant-minimal) to highlight library issues.

Occasionally, IBM Cloudant receives support tickets that state that “IBM Cloudant is broken because my application is slow” without much in terms of supporting evidence. Nearly always this case can be traced back to issues in the application code on the client side, or misconceptions about how IBM Cloudant works.

Not always, but nearly always.

By understanding the API better, you also gain experience in how IBM Cloudant behaves, especially in terms of performance. If you’re using a client library, you must aim to at least know how to find out which HTTP requests are generated by a specific function call. For more information, see the following websites:



* IBM Cloudant [API docs](https://cloud.ibm.com/apidocs/cloudant)
* Logging [integration](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-log-analysis-integration)
* Blog post on [logging](https://blog.cloudant.com/2019/09/16/Cloudant-Logging-with-LogDNA.html)







 Documents must group data that mostly changes together 

When you start to model your data, sooner or later, you run into the issue of how your documents might be structured. Now you know that IBM Cloudant doesn’t enforce any normalization and that it has no transactions of the type you’re used to from, say, [Postgres](https://www.postgresql.org/). The temptation can be to cram as much as possible into each document, which would also save on HTTP usage.

This practice is often a bad idea.

If your model groups information that doesn’t change together, you’re more likely to suffer from update conflicts.
Figure 1. EDA diagram





 Weather (WRF Model) 

IBM Cloud shows linear performance, performs favorably, and can scale well into thousands of cores. The virtual machine configuration that is used for this benchmark is bx2-16x64. The WRF model is not sensitive to network latency as it packs many variables into each message, resulting in fairly large messages, and not many small messages.

Zoom

![EDA-diagram](https://cloud.ibm.com/docs-content/v1/content/74a831a53989757bd05bd0dea7bb42c9ede61d0f/ibm-spectrum-lsf/images/Weather.png)

Figure 2. WRF diagram

The red line represents the HPC environment with the InfiniBand HDR that gives highest bandwidth, lowest latency, and is the best configuration for such workloads. The green line shows IBM Cloud with the Lon2 data center for the benchmarking. The blue line is Summit super computer. In summary, any workloads that have characteristics similar to the WRF model should scale well with IBM Cloud. As you can see IBM Cloud shows reasonable performance against state-of-the-art HPC systems.





 DoE (Department of Energy) benchmarking 

SNAP and Quicksilver are two applications that the DoE uses for benchmarking and making decisions on specific commodity technology systems.

The following graphs show results on how IBM Cloud compares with the state-of-the-art HPC system.

On IBM Cloud, the benchmarks used two different configurations:



* bx2-8x32
* bx2-16x64



As you can see, SNAP results show that bx2-8x32 provides more performance because of higher effective network bandwidth ratio per core; where Quicksilver does well with bx2-16x64 as it has moderate communication requirements and is mostly near-neighbor to track particle motion across the global domain.

Zoom

!
Here you can see the total charges and usage for the month by service, plan, or instance. Only the hourly costs that are accrued for the current month and time are available. At the end of the month, you can see the average provisioned throughput capacity for each field: LOOKUPS_PER_MONTH, WRITES_PER_MONTH, and QUERIES_PER_MONTH.



* Can I change my capacity setting?

You can change your provisioned throughput capacity and see your current capacity settings in the IBM Cloudant Dashboard. Launch IBM Cloudant Dashboard > Account > Capacity to view and change your provisioned throughput capacity and see the hourly and approximate monthly costs. You can also use the IBM Cloud® pricing calculator to see estimates in other currencies.
* How do I know I exceeded the capacity limit that I set?

The Lite plan includes 1 GB of storage. If you exceed the limit, IBM Cloudant blocks your account from writing new data until you delete enough data to be under the 1-GB limit, or upgrade to a higher plan.

The first 20 GB of storage comes free with the Standard plan. You can store as much data as you want. Any storage over the 20 GB limit costs $0.0014 per GB per hour, which is approximately $1 per GB per month.
* Where can I see my usage data?

You can see your current and historical usage bills in the IBM Cloud Dashboard. Go to Manage > Billing and usage > Usage. Here you can see the total charges and usage for the month by service, plan, or instance. Only the hourly costs that are accrued for the current month and time are available. At the end of the month, you can see the average provisioned throughput capacity for each field: LOOKUPS_PER_MONTH, WRITES_PER_MONTH, and QUERIES_PER_MONTH.
* Provisioned throughput capacity model FAQ

 Provisioned throughput capacity model FAQ 

IBM® Cloudant® for IBM Cloud® calculates your provisioned throughput capacity based on these operation types: Read, Write, and Global Query.



IBM Cloudant calculates provisioned throughput capacity by totaling the usage for each request class per second, where 1 second is a sliding window.
As a result of this transition, existing users might meet or exceed the lite plan limit on documents (2000), storage (200Mb), or number of collections (2). If you exceed the limit of the Lite plan, you cannot add any additional content into the service, but you can still query collections. : View the current status of all these limits by using the Discovery tooling or API. To resume adding content to the Discovery instance, you must complete one of the following actions: : Remove collections or documents so that limits of the Lite plan are not exceeded. : You can delete documents either individually in the API, using the [delete-doc](https://cloud.ibm.com/apidocs/discoverydelete-a-document) method, or you can delete whole collections, using the tooling or API, by using the [delete-collection](https://cloud.ibm.com/apidocs/discoverydelete-a-collection) method. : Upgrade your plan to a level that meets your storage needs. : Customers with size 12 or 3 environments will be automatically migrated to the Advanced plan.





 17 July 2017 

Update to relevancy training, natural language query, and highlighting : Relevancy training announced on 23 June 2017 moved from beta to GA status. : Natural language query announced on 19 June 2017 movedd from beta to GA status. : Highlighting announced on 25 May 2017 moved from beta to GA status.

Update to enrichment mechanism : IBM Watson™ Discovery is changing its enrichment mechanism from AlchemyLanguage to Natural Language Understanding as of this release. : AlchemyLanguage is in the process of being deprecated, so it is recommended that you start using Natural Language Understanding as soon as possible. : If you integrate with Watson Knowledge Studio, you must still use the AlchemyLanguage enrichment configuration. For details, see [Integrating with IBM Watson™ Knowledge Studio](https://cloud.ibm.com/docs/discovery?topic=discovery-integrating-with-wks).

Update to version string : The version string for all API calls changed to 2017-07-19 from 2017-06-25. This version enables an NLU default config on collection creation.
Can I create more than one Object Storage service with a Lite account? 

If you already have a Lite plan instance created, you may create other Standard plan instances, but only one Lite plan instance is allowed.





 What happens if I exceed the maximum usage allowed for a Lite plan? 

Once you exceed the allowed usage, the service instance associated with the Lite plan becomes inaccessible. You will receive a warning notification email with corrective steps. If you do not take action, the instance is removed.
: The Plus plan is now available from the London and Washington DC locations, in addition to Dallas, Frankfurt, and Tokyo.

Change to Lite and Advanced plans in some locations
: You cannot create new service instances that use the Lite or Advanced plan types in the Dallas, Frankfurt, London, Tokyo, or Washington DC locations. 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.

New answer finding feature
: Answer finding is now generally available for managed deployments. Use answer finding when you want to return a concise answer to a question. For more information, see [Answer finding](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-query-parametersanswer-finding).





 16 August 2021 

New locations for the Plus plan
: The Plus plan is now available from the Frankfurt and Tokyo locations, in addition to Dallas.

Change to Lite and Advanced plans in some locations
: 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, Frankfurt, or Tokyo locations. 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.





 27 July 2021 

Improved document size limit
: Document size limit is increased. For Premium plan collections, you can now upload files that are up to 50 MB in size instead of 32 MB. For more information, see [Document limits](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collectionscollections-doc-limits).





 23 July 2021 

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).
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.







 Why don't I see the Analytics page? 

To view the Analytics page, you must have a service role of Manager and a platform role of at least Viewer. For more information about access roles and how to request an access role change, see [Managing access to resources](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-access-control).





 Why am I unable to view the API details, API key, or service credentials? 

If you cannot view the API details or service credentials, it is likely that you do not have Manager access to the service instance in which the resource was created. Only people with Manager access to the instance can use the service credentials.





 Can I export the user conversations from the Analytics page? 

You cannot directly export conversations from the conversation page. However, you can use the /logs API to list events from the transcripts of conversations that occurred between your users and your assistant. For more information, see the [V2 API reference](https://cloud.ibm.com/apidocs/assistant/assistant-v2listlogs). Or, you can use a Python script to export logs. For more information, see [export_logs_py](https://github.com/watson-developer-cloud/community/blob/master/watson-assistant/export_logs_py.py).





 Can I change my plan to a Lite plan? 

No, you cannot change from a Trial, Plus, or Standard plan to a Lite plan. And you cannot upgrade from a Trial to a Standard plan.





 How many Lite plan instances of Watson Assistant can I create? 

You can have only one Lite plan instance of Watson Assistant per resource group.





 How do I create a webhook?
For more information, see [export_logs_py](https://github.com/watson-developer-cloud/community/blob/master/watson-assistant/export_logs_py.py).





 Can I change my plan to a Lite plan? 

No, you cannot change from a Trial, Plus, or Standard plan to a Lite plan. And you cannot upgrade from a Trial to a Standard plan.





 How many Lite plan instances of Watson Assistant can I create? 

You can have only one Lite plan instance of Watson Assistant per resource group.





 How do I create a webhook? 

To define a webhook and add its details, go to the Live environment page and open the Environment settings page. From the Environment settings page, click Webhooks > Pre-message webhook. You can add details about your webhook. For more information, see [Making a call before processing a message](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-webhook-pre).





 Can I have more than one entry in the URL field for a webhook? 

No, you can define only one webhook URL for an action. For more information, see [Defining the webhook](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-webhook-prewebhook-pre-create).





 Is there a range of IP addresses that are being used by a webhook? 

Unfortunately, the IP address ranges from which Watson Assistant might call a webhook URL are subject to change, which in turn prevent using them in any static firewall configuration. Use the https transport and specify an authorization header to control access to the webhook.





 What do I do if the training process seems stuck? 

If the training process gets stuck, first check whether for an outage for the service by going to the [Cloud status page](https://cloud.ibm.com/status). You can start a new training process to stop the current process and start over.





 How do I see my monthly active users in Watson Assistant?
If needed, first back up your data, delete your current Lite plan instance to create a new one, then load your data. You cannot change the email address associated with an existing Db2 Lite instance if you have only a Lite account with community support.
* I am having trouble with reactivation. What should I do?

If you have trouble with reactivation of a Lite plan instance, you can delete that faulty instance and create a new one. If needed, first back up your data so you can load it to this new instance.
* I'm getting an error when creating a new instance. What's the problem?

There's a limit of one instance per Lite plan. You may see an error 500 message if you try to create a second Lite instance. To create a new Lite plan instance, you must first delete your existing one.
* I'm getting an error when creating a new schema or database. What's the problem?

The free Lite plan does not allow you to create new schemas or databases. There is an existing schema created for you to use. Use that schema.
* Why can’t I open the web console?

If the Db2 web console does not load or returns an error message, try the following steps:



* Go to the service page to check whether your Lite instance has expired. The Open Console button no longer appears for expired instances. Delete the expired instance and create a new one.
* Try using the direct URL to open the console to check for errors. Select the Service credentials tab from your service page and expand the credentials that you want to view. If there are no existing credentials, click New credential. Use the values in the https_url, username, and password to open the web console.
* To reset the password, select the Service credentials tab from your service page and then delete the existing service lite-tier service credential. Then click New credential to generate a new password for the existing username.
* When you create a Lite instance, be sure to provide an email address so you receive reactivation notices and password reset notices.