vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Applying subscription codes 

After you buy a subscription for platform or support credit, you must add the credit to your account by applying a subscription code to an existing account or a new account when you register. Applying the code ensures that the credit is added to your account and you don't have unexpected overage charges.

If you set up your first subscription through the [Subscriptions page](https://cloud.ibm.com/billing/subscriptions), the credit for this subscription is automatically added to your account - no code required.

After IBM Cloud Sales places the order, an email with the subscription code for each subscription and support line item is sent to the appropriate contact.

Only the account owner, enterprise account owner, or a user with the Editor or Administrator role on the Billing account management service can apply the subscription code. If you don't have access to apply subscription codes, the account owner or administrator can provide access. For more information, see [Assigning access to account management services](https://cloud.ibm.com/docs/account?topic=account-account-services). Applying the subscription code through the IBM Cloud® console is essential to ensure that your account is migrated appropriately.



1. Open the email with the subscription code.

If you bought a subscription and didn't receive your subscription code, [contact us](https://www.ibm.com/cloud?contactmodule) or email Sales at [CloudDigitalSales@us.ibm.com](mailto:CloudDigitalSales@us.ibm.com) to request for it to be sent again.
2. Click Add subscription to add it to an existing account.
3. Sign in to the console with your IBMid and password.
4. From the modal, choose the account you'd like to add the subscription to, select I understand, and then click Add.



To manually apply the subscription code to an existing account, complete the following steps:



1. In the IBM Cloud® console, go to Manage > Account, and select Account settings.
2. Click Apply code.

Each code can be redeemed only one time, and the codes must be redeemed before their expiration date.
See [Getting started with subscriptions](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribing-events) for more information about working with subscriptions in Code Engine.

You can use either subscription or sub in your subscription cron commands. To see CLI help for the subscription cron command, run ibmcloud ce sub cron -h.



 ibmcloud ce subscription cron create 

Create a cron event subscription.

ibmcloud ce subscription cron create --name CRON_SOURCE_NAME --destination DESTINATION_REF [--content-type CONTENT_TYPE] [--data DATA] [--data-base64 DATA_BASE64] [--destination-type DESTINATION_TYPE] [--extension EXTENSION] [--force] [--no-wait] [--output OUTPUT] [--path PATH] [--quiet] [--schedule SCHEDULE] [--time-zone TIME_ZONE] [--wait] [--wait-timeout WAIT_TIMEOUT]



 Command Options 

--destination, -d
: The name of the application or job resource that you want to receive events; for example, myapp. If needed, use the --path option to further qualify an app destination. This value is required.

-n, --name
: The name of the cron event subscription. Use a name that is unique within the project.



* The name must begin and end with a lowercase alphanumeric character.
* The name must be 253 characters or fewer and can contain lowercase letters, numbers, periods (.), and hyphens (-).



This value is required.

--content-type, --ct
: The media type of the --data or --data-base64 option. Examples include application/json, application/x-www-form-urlencoded, text/html, and text/plain. This value is optional.

--da, --data
: The data to send to the destination; for example, '{ "message": "Hello world!" }'.
If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI0700E 

Message: The ‘{0}’ space wasn't created because a problem occurred contacting Cloud Foundry.

Click Create to try again or cancel the action.





 BXNUI0701E 

Message: Failed to invite users. Error Code: errorCode.

Try again later. If you see this message again, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI0702E 

Message: Failed to invite emailAddress. Error Code: errorCode.

Try again later. If you see this message again, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI0703E 

Message: The details for this invited user are currently unavailable.

Try again later.





 BXNUI0704E 

Message: The details for this invited user could not be loaded from the following region or regions: regions.

Try again later.





 BXNUI2000E 

Message: The request was not processed because of an error. This exception was issued: {0}

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2001E 

Message: No Ant build.xml file exists for the "{0}" starter.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2002E 

Message:No builder exists for the "{0}" starter.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2004E 

Message: The app was not created because of an error from the cloud server.

Try again.
329Z ERROR apiConnect: listen EADDRINUSE <ip address> :9000

 Why it’s happening 

You have already started an instance of the API Designer from another command window.

 How to fix it 

To fix this problem, you need to close the other command window as described in the following steps:



1. In the other command window, press Ctrl + C.
2. The following message is displayed.



Terminate Batch job (Y/N)?



3. Type Y and press Enter.







 Cannot configure billing information for a Product 

Some of the billing information is not available to configure or commit to production.



* What’s happening
* When you look at the Admin section of your Product, the Billing tab is not displayed.
* When you try to publish a Product with the billing information specified, you get an error.



 Why it’s happening 

You must have the correct API Connect account and permissions to enable billing information.

 How to fix it 

Review [API Connect for IBM Cloud user roles](https://www.ibm.com/support/knowledgecenter/SSFS6T/com.ibm.apic.overview.doc/rapic_overview_users_cloud.html) for information about what permissions can be set.





 Cannot subscribe to a billing Plan with a Product 

Stripe limits each customer to a maximum of 25 subscriptions. Ensure that you have not exceeded this limit. If so, you can only add this subscription if you remove another subscription.

 What’s happening 

You see an error when you try to subscribe to a Plan with billing, though you have other Plans configured.

 Why it’s happening 

The Stripe credit card processing service allows a maximum of 25 subscriptions per account.

 How to fix it 

Ensure that you have an Enterprise level account for your API Connect service, and that there are fewer than 25 instances. If you already have the maximum number of instances, remove an instance.





 Getting help and support for API Connect 

If you have problems or questions when using API Connect, you can get help by searching for information or by asking questions through a forum. You can also open a support ticket.
You can verify the unsubscribed state by running the following command. See the following example:

[root@skv-vsic1x7im ] subscription-manager list
You are attempting to use a locale that is not installed.
+-------------------------------------------+
Installed Product Status
+-------------------------------------------+
Product Name: Red Hat Enterprise Linux Server
Product ID: 69
Version: 7.9
Arch: x86_64
Status: Unknown
Status Details:
Starts:
Ends:

[root@skv-vsic1x7im ]
2. Run the subscription script /var/lib/cloud/instances/(VSI/Instance ID)/scripts/vendor/part-00* which contains the register subscription() function. When the script is complete the operating system is subscribed. See the following example:

[root@skv-vsic1x7im ]./var/lib/cloud/instances/0727_60b2078d-8e30-4c66-a894-b1fbd0ed7acf/scripts/vendor/part-004

After the script completes, verify the details. See the following example:

[root@skv-vsic1x7im ] subscription-manager list
You are attempting to use a locale that is not installed.
+-------------------------------------------+
Installed Product Status
+-------------------------------------------+
However, the table on the subscriber must contain at least every column present in the table on the publisher. Additional columns present in the subscriber must not have NOT NULL or other constraints. If they do, replication fails.



Note Native PostgreSQL subscription commands require superuser privileges, which are not available on Databases for PostgreSQL deployments. Instead, your deployment includes a set of functions that can be used to set and manage logical replication for the subscription.

Only the admin user that is provided by Databases for PostgreSQL has permissions to run the following replication commands that allow you to subscribe and replicate content from an external PostgreSQL publisher.



 Subscriber Functions 

create_subscription

Arguments:
subscription_name Unique name to create the subscription channel with
host_ip Publisher hostname or public IP address
port Port number publisher is running on
username admin user created on the publisher
password Password of the admin user on the publisher
db_name The name of the database to be replicated
publisher_name The name of publisher channel on the publisher

Usage:
exampledb=> SELECT create_subscription('subs1','130.215.223.184','5432','password','admin','exampledb','my_publication');

delete_subscription

Arguments:
subscription_name Name the subscription channel to delete
db_name The name of the replicated database

Usage:
exampledb=> SELECT delete_subscription('subs1', 'exampledb');

list_subscriptions

Arguments:
None

Usage:
exampledb=> SELECT * FROM list_subscriptions();

disable_subscription

Arguments:
subscription_name Name the subscription channel to disable
db_name The name of the replicated database

Usage:
exampledb=> SELECT disable_subscription('subs1','exampledb');

enable_subscription

Arguments:
subscription_name Name the subscription channel to enable
db_name The name of the replicated database

Usage:
Why is my subscription cron create command failing? 

 What’s happening 

You cannot create a cron subscription through the CLI by using the [ibmcloud ce subscription cron create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cron-create) command and you receive an error that mentions failed in the message.

 Why it’s happening 

If you cannot create a cron subscription, determine whether one of the following cases is true.



1. The name of your subscription is not unique within the project.
2. The application or job reference doesn't exist. An error with text similar to the following message appears: Failed to retrieve the application. View available applications by running ibmcloud ce app list.



 How to fix it 

Try one of these solutions.



1. Run the [ibmcloud ce sub cron list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cron-list) command to list all defined cron subscriptions and check whether a subscription with the same name exists. If a subscription with the same name exists, use the [ibmcloud ce sub cron delete --name SUB_NAME](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cron-delete) command to delete the old subscription. The name of the subscription must be unique within your project.
2. Run [ibmcloud ce app list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-list) or [ibmcloud ce job list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-list) to make sure that your destination app or job exists.
Why is my subscription cos create command failing? 

 What’s happening 

You cannot create an IBM Cloud Object Storage subscription through the CLI by using the [ibmcloud ce subscription cos create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-create) command and you receive an error that mentions failed in the message.

 Why it’s happening 

If you cannot create an Object Storage subscription, determine whether one of the following cases is true,



1. The name of your subscription is not unique within the project.
2. The application or job reference doesn't exist. An error with text similar to the following message appears: Failed to retrieve the application. View available applications by running ibmcloud ce app list.
3. A timeout occurs. Error message mentions Getting COS event subscription status timed out



 How to fix it 

Try one of these solutions.



1. Run the [ibmcloud ce sub cos list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-list) command to list all defined Object Storage subscriptions and check whether a subscription with the same name exists. If a subscription with the same name exists, run the [ibmcloud ce sub cos delete --name SUB_NAME](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-delete) to delete the old subscription. The name of the subscription must be unique within your project.
2. Run [ibmcloud ce app list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-list) or [ibmcloud ce job list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-list) to make sure that your destination app or job exists.
"more_info": "https://docs.api.example.com/v2/users/create_userusername",
"target": {
"type": "field",
"name": "username"
}
}
]
}
Show more







 Codes and messages 

Error code values SHOULD specify the problem that caused an error; message values SHOULD describe the problem and MAY also provide suggestions or solutions.



 Codes 

Error code values MUST be snake case strings, descriptive of the problem encountered, as succinct as possible, and absent of any non-standard or proprietary terms, brands, codenames, abbreviations, or acronyms.

code values SHOULD NOT prescribe solutions to problems. For example, color_must_be_red_or_blue is not a good code. A better code would be invalid_color, leaving solutions to message values. This allows code values to remain constant even if a field becomes more permissive in the future.

A code value, along with any other machine-readable fields included in an error, SHOULD be specific enough for client code to take any required action. Client code should not be forced to parse a human-readable message value in order to take action on a specific error condition.

The documentation for specific requests SHOULD enumerate possible error code values. Adding a possible error code for a request SHOULD be considered a breaking change. For this reason, the documentation MAY include possible error code values which are not yet used.





 Messages 

Error message values SHOULD describe the problems identified by code values in complete, well-formed sentences and MAY provide suggestions or solutions. It is expected for message values to duplicate information from code, target, and custom extensions to the error model.

Importantly, message values are still meant for developers and for this reason SHOULD NOT be localized or written for use in a user interface. Fields mentioned within a message SHOULD be mentioned by exact field name (e.g., first_name, not "first name").

Consider the example above of an error code with value invalid_color. A poor message would be:

"The color provided for paint was invalid."
After you define an IBM Cloud Object Storage event subscription that references a specific bucket, you cannot update this subscription to use a different bucket. You must create a new subscription to reference the bucket that you want.





 Subscribing to IBM Cloud Object Storage events for an application with the CLI 

Before you begin



* [Set up your Code Engine CLI environment](https://cloud.ibm.com/docs/codeengine?topic=codeengine-install-cli).
* [Create and work with a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).
* Create an application. For example, create an application that is called myapp that uses the icr.io/codeengine/cos-listen image. This image is built from cos-listen.go, available from the [Samples for IBM Cloud Code Engine GitHub repo](https://github.com/IBM/CodeEngine/tree/main/cos-event). For example,

ibmcloud ce application create --name myapp --image icr.io/codeengine/cos-listen





1. Connect your application to the IBM Cloud Object Storage event producer by using the [ibmcloud ce subscription cos create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-create) command. For example,

ibmcloud ce subscription cos create --name mycosevent --destination-type app --destination myapp --bucket mybucket
2. After your subscription creates, run the subscription cos get command for details about your subscription.

ibmcloud ce subscription cos get --name mycosevent

Example output

Getting COS source 'mycosevent'...
OK

Name: mycosevent
ID: abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Project Name: myproject
[Register new app](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/34-create-new-app.png)
5. Enter a Title and Description for your app and select Submit.
![Submit new app](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/35-submit-new-app.png)
6. Now that you have an App, you can subscribe to API Product plans. Select available APIs or API Products to browse the API Product plans.
![API Details](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/36-api-products.png)
7. Select the API Product you want to subscribe to.
![API Product](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/37-select-product.png)
8. Select Subscribe to subscribe to the API Product Plan.
![API Product Plan](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/38-subscribe-plan.png)
9. Select the app that you want to subscribe to the product Plan, then select Subscribe. !
Why does my subscription show errors when it delivers events? 

 What’s happening 

Subscription events were created, but errors are received when events are delivered to your Code Engine application or job.

 Why it’s happening 

Check to see whether one of the following cases is true.



1. Does the subscription destination application or job exist?
2. Is the destination app or job prepared and looking for HTTP POST messages?



 How to fix it 

Look at the subscription source to see whether any error messages are returned. For IBM Cloud Object Storage subscriptions, use the [ibmcloud ce sub cos get --name SUB_NAME](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-get) command. For cron subscriptions, use [ibmcloud ce sub cron get --name SUB_NAME](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cron-get) command.



1. Confirm that your subscription destination exists.



* If your subscription destination is an application, use the [ibmcloud ce app list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-list) command to confirm that your application exists and that it wasn't deleted. Check that the status of your application is Ready. You can also use the [ibmcloud ce app get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-get) command to display the status of the application.
* If your subscription destination is a job, use the [ibmcloud ce job list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-get) command to confirm that your job exists.
To apply the code, select a billable plan, enter the promo code, and click Apply. The promo code is added to your account even if you don't create the service.

Existing classic infrastructure promo codes can be applied only through the catalog when you create those classic infrastructure services. To apply these promo codes, you must have one of the following classic infrastructure permissions on the account: add or upgrade storage, add or upgrade services, or add server. For more information, see [Classic infrastructure permissions](https://cloud.ibm.com/docs/account?topic=account-infrapermission).





 Viewing your promotions 

You can view details about active promotions in your account, including your promotion start and end dates and the history of redeemed promo codes, from the table on the Promotions and credits page.



1. In the IBM Cloud console, go to Manage > Billing and usage, and select Promotions and credits.
2. Click a promotion to expand the table and view a description of each promotion and the products it applies to.



You can search for specific promotions, or you can filter by the status or type of promo code. To filter by status, you can select Active, Upcoming, Expired or All promotions. To filter by the type of promo code, you can select One-time, Recurring, or All promotions.

Promo codes can't be removed from your account, but they expire and become inactive when they reach their end date.
See [Getting started with subscriptions](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribing-events) for more information about working with subscriptions in Code Engine.

You can use either subscription or sub in your subscription kafka commands. To see CLI help for the subscription commands, run ibmcloud ce sub kafka -h.



 ibmcloud ce subscription kafka create 

Create a Kafka event subscription.

ibmcloud ce subscription kafka create --name KAFKA_SOURCE_NAME --destination DESTINATION_REF --topic TOPIC --broker BROKER [--consumer-group CONSUMER_GROUP] [--destination-type DESTINATION_TYPE] [--extension EXTENSION] [--force] [--no-wait] [--output OUTPUT] [--password PASSWORD] [--path PATH] [--quiet] [--secret SECRET] [--username USERNAME] [--wait] [--wait-timeout WAIT_TIMEOUT]



 Command Options 

--broker, -b
: Set a broker in the Kafka source. A broker is a Kafka server to which the consumer connects. This option can be specified multiple times. This value is required.

--destination, -d
: The name of the application or job resource that you want to receive events; for example, myapp. If needed, use the --path option to further qualify an app destination. This value is required.

-n, --name
: The name of the Kafka event subscription. Use a name that is unique within the project.



* The name must begin and end with a lowercase alphanumeric character.
* The name must be 253 characters or fewer and can contain lowercase letters, numbers, periods (.), and hyphens (-).



This value is required.

--topic, -t
: Set a topic in the Kafka source. Topics are used to filter messages to consume. This option can be specified multiple times. This value is required.

--consumer-group, --cg