vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The minimum timeout is 300 seconds and the maximum 3600 seconds. This request fails a source file share over to the replica share, which is specified by the replica file share ID.

By default, the fallback_policy property has the value fail. In this case, if the failover operation fails or the timeout is reached, the failover operation is unsuccessful.

If you specify split for the failback_policy property, the replica share is split from the source share whenever a failover operation fails. The result is two independent read/write file shares. In this case, because the final file synchronization could not complete, the replica share might not contain all the data of the source file share. Use this option for disaster recovery, when the source file share is known to be unreachable.

As described in the [Beta VPC API](https://cloud.ibm.com/apidocs/vpc-beta) reference [versioning](https://cloud.ibm.com/apidocs/vpc-betaapi-versioning-beta) policy, support for older versions of the beta API is limited to 45 days. Therefore, beta API requests must specify a version query parameter date value within the last 45 days. You must also provide generation parameter and specify generation=2. For more information, see Generation in the [Virtual Private Cloud API reference](https://cloud.ibm.com/apidocs/vpcapi-generation-parameter).

This example specifies fail for the fallback_policy property, which is the default. It's provided here as an example but you could leave it blank. The timeout property is also optional. You can use the default timeout.

curl -X POST "$vpc_api_endpoint/v1/shares/$replica_id?/failover?version=2023-06-20&generation=2"&maturity=beta -H "Authorization: $iam_token" -d '{
"fallback_policy": "fail",
"timeout": 600
}'

A successful response indicates that the file share failover request was accepted.
Providing options when a question or request can't be answered 

No matter how well your assistant is designed, sometimes customers can run into problems getting it to understand them or do what they want. Your assistant can automatically help customers recover from many such situations, and you can configure how it responds.



 How error conditions are handled 

There are several kinds of error situations your assistant might need to recover from:



* Your assistant cannot understand your customer's request
* Your customer does not provide a valid response to a question
* Your customer asks to talk to a live agent



Your assistant can detect error conditions and give customers the chance to correct them. In addition, the built-in Fallback action provides a way to automatically connect customers to a live agent if they need more help.



 When the assistant can't understand your customer's request 

When you build actions, you train your assistant on what your customers might ask for. The Customer starts with section of each action provides examples of customer input that trigger the action; the assistant uses natural language processing to recognize customer input that is similar to these examples. This happens at the beginning of the conversation, or after any action has completed and the assistant is ready for another action.

But you can't anticipate every possible request, so sometimes customers will send input that your assistant can't match to any action. This might happen because the input isn't phrased in a way that the assistant can understand; it can also happen if customers ask for things that your assistant isn't designed to handle.

Unrecognized input of this sort triggers the built-in No action matches action. To see how this action works, click Set by assistant in the list of actions, and then click No action matches.

Zoom

![No action matches built-in action](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/no-action-matches.png)

No action matches built-in action

By default, this action has two steps, each step conditioned on the No action matches count session variable.
For more information, see [When your customer asks to speak to a live agent](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-handle-errorswhen-your-customer-asks-to-speak-to-a-human-agent). Or, the user chooses human agent escalation from the list of [suggestions in web chat](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-deploy-web-chatdeploy-web-chat-alternate). 
 Started a new action The user changes the topic of the conversation, triggering another action, and either doesn't return to the original action or the other action is also incomplete. 
 Stuck on a step Triggered during step validation where a user exceeds the maximum retries for the particular step. Default tries is set to 3, but you can change this setting. See [Customizing validation for a response](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-handle-errorscustomizing-validation-for-a-response) for more information. 
 Abandoned An action is considered abandoned if it was not completed after 1 hour of inactivity and doesn't meet the criteria for any other incompletion reason (escalated to agent, started a new action, or stuck on a step). 









 Improving completion 

To help you identify actions that need improvement, the Action completion page is organized into a How often chart and an Actions table. The How often chart shows either the percentage of complete actions or the number of complete and incomplete actions during a timeframe. Use the icon in the upper right of the chart to toggle between a line chart that shows the percentage of complete actions or a bar chart that shows the number of complete and incomplete actions. The Actions table provides number of requests, total incomplete, and completion percentage per action.

![Action completion](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/analytics-action-completion.png)
ibmcloud hpvs instance-delete CRN --force



Where CRN is Cloud resource name of the server you want to delete. Use --force to force the deletion of the Hyper Protect Virtual Servers instance without showing a confirmation prompt.

You can find more information and example output [here](https://cloud.ibm.com/docs/hpvs-cli-pluginhpvs-instance-delete).





 What happens during the reclamation period 

When you delete a virtual server from the resource list, the server isn't deleted immediately, it's stopped and marked for deletion, and a reclamation period of seven days starts. The server is deleted after the reclamation period ends. During this seven-day reclamation period, you can restore the virtual server, or manually trigger a deletion from [resource reclamations](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_reclamations). Resource reclamations lists the Hyper Protect Virtual Servers that are marked for deletion together with the time (Target time) when the actual deletion is triggered.





 Deleting servers that belong to the free plan 

The free plan servers expire 30 days after they are created. When a server expires, it's immediately deleted at the backend. The server is also deleted at the backend if it expires during the seven-day reclamation period. Even though the server is deleted at the backend, it's still displayed in the resource list or in the resource reclamations as if it still exists.

If the server has expired, you can remove the entry from the resource list and either:



* Wait for the target time to trigger deletion for you, or
* Manually trigger the deletion from the resource reclamations.



If an expired server is restored, only the entry within the resource list is restored, not the server itself.





 Restoring servers that belong to paid plans 

Servers that belong to a paid plans do not expire, and that's why they can be restored during the reclamation period.
When you enable a rule, some users, applications, and workflows might be affected. If your users or applications can't access something that they previously had access to, you can search in Activity Tracker and view what rules are denying the requests. You can further refine the search by filtering on the subject or resource to identify the implicated rule, which is represented by the target id. Then, you can update the rule to allow access so that your workflows don't break. For more information, see [Updating context-based restrictions](https://cloud.ibm.com/docs/account?topic=account-context-restrictions-update).

Complete the following steps to view how enabled rules affect your users' and applications' access by using Activity Tracker:



1. In the IBM Cloud console, go to the Navigation menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/icon_hamburger.svg) > Observability > Activity Tracker.
2. Click Open dashboard on the dashboard that you use to monitor context-based restrictions.
3. Use the search field to narrow the results to enabled context-based restrictions events.



1. To view blocked access request, search for action:context-based-restrictions.policy.eval responseData.isEnforced:==true responseData.decision:Deny.



* isEnforced:==true indicates that the rule is enabled and enforced.
* responseData.decision:Deny indicates that the access request is blocked.



2. If you have a specific resource that you are protecting with a context-based restriction, you can see whether access to the resource is blocked by searching for action:context-based-restrictions.policy.eval responseData.decision:Deny responseData.isEnforced:==true <CRN OR UNIQUE ID OF THE RESOURCE>.







 Examples 

A context-based restriction rule that protects Example service has the following identifying attributes in Activity Tracker:



Table 1.
Security Assessment and Authorization (CA) [CA-3 System Interconnections](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ca-3) 



8. Set the session inactivity timeout to 15 minutes. For more information, see [Setting the sign-out due to inactivity duration](https://cloud.ibm.com/docs/account?topic=account-iam-work-sessionssessions-inactivity).

The following table shows the controls that are most related to this step.



Table 6. Related controls in IBM Cloud Framework for Financial Services for using only session inactivity timeout

 Family Control 

 Access Control (AC) [AC-11 Session Lock](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-11) 



9. [Update company profile details](https://cloud.ibm.com/docs/account?topic=account-contact-info).

The following table shows the controls that are most related to this step.



Table 7. Related IBM Cloud Framework for Financial Services controls for updating company profile details

 Family Control 

 Configuration Management (CM) [CM-8 (4) Information System Component Inventory | Accountability Information](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-cm-8.4) 



10. [Set email preferences for notifications](https://cloud.ibm.com/docs/account?topic=account-email-prefs). You can receive email notifications about IBM Cloud platform-related items, such as announcements, critical events, security notices, billing and usage, and ordering.

The following table shows the controls that are most related to this step.



Table 8. Related IBM Cloud Framework for Financial Services controls for configuring notifications

 Family Control
--activation-date-min (string)
: Optional. Return only managed keys whose activation date is at or after the parameter value. This query parameter cannot be used in conjunction with the activation_date query parameter. The value must match regular expression /[0-9]{4}-[0-9]{2}-[0-9]{2}/.

--activation-date-max (string)
: Optional. Return only managed keys whose activation date is at or before the parameter value. This query parameter cannot be used in conjunction with the activation_date query parameter. The value must match regular expression /[0-9]{4}-[0-9]{2}-[0-9]{2}/.

--deactivation-date (string)
: Optional. Return only managed keys whose deactivation date matches the parameter. This query parameter cannot be used in conjunction with the expiration_date query parameter. The value must match regular expression /[0-9]{4}-[0-9]{2}-[0-9]{2}/.

--deactivation-date-min (string)
: Optional. Return only managed keys whose deactivation date is at or after the parameter value. This query parameter cannot be used in conjunction with the deactivation_date, expiration_date, expiration_date_min, and expiration_date_max query parameters. The value must match regular expression /[0-9]{4}-[0-9]{2}-[0-9]{2}/.

--deactivation-date-max (string)
: Optional. Return only managed keys whose deactivation date is at or before the parameter value. This query parameter cannot be used in conjunction with the deactivation_date, expiration_date, expiration_date_min, and expiration_date_max query parameters. The value must match regular expression /[0-9]{4}-[0-9]{2}-[0-9]{2}/.

--expiration-date (string)
: Optional.
Why does a resource group error occur after reactivation or upgrade of a suspended account? 

When you try to reactivate or upgrade a closed Lite account, the process does not complete successfully.

  What’s happening 

The following error message displays when you try to create a new service instance:

> The resource group <name> is inactive with state: SUSPENDED

Or when you view the list of resource groups for the account, you no longer have a group named Default.

  Why it’s happening 

This is a known issue and limitation for deactivated accounts that have been restored. At the discretion of IBM, accounts that violate the acceptable usage behavior of the IBM Cloud® services can be deactivated without notice. Some services can be restored if users correct their usage behaviors after they're notified of the offensive action. For more information, see [Acceptable Internet use policy for IBM services](https://www.ibm.com/services/us/imc/html/aup1.html).

  How to fix it 

To resolve the issue, [create a support case](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case) and include the group name from the error message in the case details.
Why do I get the message "You do not have permission to perform this action." when trying to use the Event Notifications service instance? 

When you try to use Event Notifications service instance you are unable to perform any action.

  What’s happening 

When you try to access any feature in Event Notifications service instance either through the console or API or CLI, you may encounter an error similar to any of the following examples:

You do not have permission to perform this action. Contact your service Administrator.

or

{
"message": "Unauthorized"
}

  Why it’s happening 

This is due to the reason that you are trying to access the Event Notifications service instance from a Network Zone which is outside of the defined Network zone in your account's Context-based restrictions settings.

  How to fix it 

To resolve the issue, make sure that your Context-based restrictions settings in the account are updated to allow the IP addresses that correspond with your network in the Network Zone's Allowed IP addresses.

As an administrator of your Event Notifications service instance perform the following steps:



1.  In the IBM Cloud console, click Manage > Context-based restrictions.
2.  Go to Network zones and then select the required Network Zone and select Edit from the overflow menu.
3.  In the Allowed IP addresses, include the required IP addresses that you want to enable access to the Event Notifications service instance.
4.  Click Update.



For more information, see [Managing access with context-based restrictions](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-access-control-cbr).
For more information, see [Granting administration permissions to a user or service ID](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-iam_manage_events).







 Configure the account settings for authentication into your account 

Multi-factor authentication (MFA) adds an extra layer of security to your account by requiring all users to authenticate by using an additional authentication method beyond an ID and password. This is also commonly known as two-factor authentication (2FA).

The IBM Cloud account owner or administrator for the billing service can choose to require multi-factor authentication (MFA) for every user in the account or just users with non-federated IDs who do not use SSO. All users with an IBMid use a time-based one-time passcode (TOTP) MFA method, and any users with a different type of ID must be enabled to use the time-based one-time passcode authentication (TOTP), security questions, or an external authentication method separately. [Learn more](https://cloud.ibm.com/docs/account?topic=account-enablemfa).

You can also configure MFA options such as security questions, using a time-based one-time passcode, and using an external authentication method. These types of MFA options are specific per account and are available only with former classic infrastructure accounts.

Enable multi-factor authentication (MFA) in your IBM Cloud account for all users.





 Define the notification strategy 

In an auditing instance, you define views to analyze the data. Then, you can configure 1 or more alerts per view to notify of an abnormal situation. [Learn more](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-alerts).

You can choose to be notified by using an absence alert that is triggered when no data is available.

Define an absence alert to be notified when inactivity in an application or service is identified. Notice that absence alerts require data in the view within the past 24 hours for the alert to be active.

You can choose to be notified by using a presence alert that is triggered when more log lines than expected are present.
You have an absence alert attached to this view that is configured to send a notification after 30 minutes. Because the view is not active, the absence alert is muted and you do not get notifications. To make the view active and get notifications for the absence condition, logs need to start flowing into the view.







 Alert conditions 

You can configure any of the following triggering conditions for each notification channel that you configure for an alert:



* Time frequency: You set this condition to specify how often to trigger an alert. Valid values are: 30 seconds, 1 minute, 5 minutes, 15 minutes, 30 minutes, 1 hour, 6 hours, 12 hours, 24 hours
* Event lines counter: You set this condition to specify the number of event lines that match the view's filtering and search criteria. When the number of event lines is reached, an alert is triggered.



You can decide whether both conditions are checked or only one. If both conditions are set, an alert is triggered when any of the thresholds is reached.

For example, you can configure an alert that is triggered after 30 seconds, or when a 100 event lines that match the view's filtering and search criteria are collected.





 Notification channels 

You can define 1 or more notification channels for an alert.

The following table lists the notification channels that you can configure when an alert is triggered:



Notification channels

 Channel Configuration details 

 email You can configure one or more email addresses. For more information, see [Integrating with email](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-email). 
 SMS You can send an SMS to notify of an alert either through the PagerDuty channel or through the IBM Cloud Monitoring channel. For more information, see [Integrating with SMS](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-sms). 
 Slack You can configure a slack channel. 
 Webhook You can configure a web hook URL. 
 PagerDuty You can configure connection details to your PagerDuty system, and select a service.
These options include the use of time-based one-time passcode authentication, security questions, third-party authentication mechanisms, and password expiration rules. For more information, see [Types of multifactor authentication](https://cloud.ibm.com/docs/account?topic=account-types).

You can regularly review the list of account users and remove users who don't need access to the account. For more information, see [Removing users from an account](https://cloud.ibm.com/docs/account?topic=account-remove).
* What is the difference between Enterprise Savings Plan and a Subscription account?

The Enterprise Savings Plan model is similar to the Subscription model. Unlike a subscription, when you have a commitment, you commit to spend a certain amount and receive discounts across the platform even after your commitment term ends. Any overage that is incurred on the account continues to receive a discount.
* How do I sign up for an Enterprise Savings Plan?

Contact [IBM Cloud Sales](https://www.ibm.com/cloud?contactmodule) to sign up for IBM Cloud Enterprise Savings Plan. To view your account ID, select "Register with a Code" during account registration. After you consult with a sales representative, you receive a confirmation email with your commitment quote details and information about IBM Cloud's Terms and Conditions. Your account is activated upon order processing.
* How do I view existing commitments?

To view your existing commitments, in the IBM Cloud® console, go to Manage > Billing and usage, and select Commitments & subscriptions.

Click the tabs to view the remaining credit in your active commitments and any upcoming commitments that aren't yet valid. A commitment is expired if its term expires or all of its credit is spent.
* How do I view my commitment usage?

To view your commitment usage, in the IBM Cloud® console, go to Manage > Billing and usage, and select Commitments & subscriptions.



* Click the tabs to view information on active or upcoming commitments.
* Use the graph to view what you've spent toward your overall committed amount.
* View monthly breakdown of the spending history for the commitment in the table.



* How do I view my commitment terms?
* Requested action can only be completed with a root key - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-key-root-req-err)
* The action could not be performed on the key because the key is expired - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-key-expired-err)
* The encrypted nonce given does not match existing record: Please ensure the correct nonce was given in the request - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-incorrect-nonce-err)
* The provided encrypted nonce was not encrypted with the key material given OR the provided IV does not match the encrypted nonce - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-incorrect-nonce-iv-err)
* This root key was created with user-supplied key material: Key material is required to perform a 'rotate' action - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-key-payload-req-err)







 HTTP 401 - Unauthorized 



* Unauthorized: The user does not have access to the specified resource - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-unauthorized-err)







 HTTP 403 - Forbidden 



* Requested change is not compliant with configuration rules - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-config_rule_conflict_err)