# Cancel Reasons

The cancel journey requires specifying a reason for cancelling. This is presented as a dropdown menu to choose from when performing the cancel action:

<figure><img src="/files/nTBNUGdPCuXOmC4YbwLc" alt=""><figcaption></figcaption></figure>

The value set for the picklist is dynamically determined by the custom metadata value stored in the Subscription Action metadata of ic Assist Config:

<figure><img src="/files/fs8oKuSPogk30SFW8Fds" alt=""><figcaption></figcaption></figure>

Values being rendered are listed in the cancelReasons array, and then retrieved in apex by the class "Get Cancel Reasons" and then stored in the flow variable CancelReasons.

<figure><img src="/files/Y4rYy0jPjlPhs3Mso84C" alt=""><figcaption></figcaption></figure>

The CancelReasons flow variable is of type list of i42as\_\_PicklistChoice.

If cancel reasons are stored somewhere else, it's possible to replace this apex action with another custom action, as long as the results are of the same type i42as\_\_PicklistChoice and then stored in the flow variable CancelReasons. The Cancel Screen flow element will read this value and render the list dynamically.

A reason for cancelling is mandatory when performing a cancel action. The values displayed can be customised and maintained by a Salesforce admin by editing the cancelReasons array within the ic Assist Config custom metadata (Subscription Action entry). Subsequent releases of the Limio for Salesforce managed package will not overwrite these values, as the metadata is designed to be user-overridable.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.limio.com/integrations/using-limio-for-salesforce/manage-subscriptions-flow/subflow-cancel/add-cancel-reasons.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.