> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/salesforce/support/troubleshooting/no-actions-available.md).

# No Actions Available on a Subscription

An agent opens a subscription and sees no actions, or does not see the action they expect. Check these causes in order.

## Start with what the agent sees

| What the agent sees                                                   | Go to             |
| --------------------------------------------------------------------- | ----------------- |
| An error screen                                                       | Cause 1           |
| No actions                                                            | Causes 2, 3 and 4 |
| One action is missing                                                 | Causes 3 and 5    |
| The action opens the wrong journey, or an Action Not Supported screen | Cause 6           |

## Cause 1: the payment provider is not set

The error "Payment provider is not configured or not supported" means that the **Payment Provider** field on the **icConfig** custom setting is empty or not valid. Enter `zuora` or `stripe`. The field is empty after an upgrade to a release with Stripe support, also on orgs that use Zuora. See [Payment Providers](/salesforce/setting-up/detailed-salesforce-setup/payment-providers.md).

If only one agent sees the error, look for a profile-level or user-level icConfig record.

## Cause 2: a rule has an empty list

When a Subscription Actions Rule matches the subscription, the agent sees only the actions in that rule. Each rule has two lists: **Actions List** for Zuora and **Actions List (Stripe)** for Stripe. If the list for your provider is empty, the agent sees no actions. Fill in that list. See [Subscription Actions](/salesforce/setting-up/additional-config/subscription-actions-rules.md).

## Cause 3: the payment provider changes the default actions

Without a rule, the default actions depend on the payment provider. See [Payment Providers](/salesforce/setting-up/detailed-salesforce-setup/payment-providers.md) for the list.

Some Zuora actions need setup. Credit Memo, Manage Add-Ons and Redeem Gift must be switched on in [Custom Metadata Types](/salesforce/setting-up/detailed-salesforce-setup/custom-metadata-types.md). Pause Print needs a `pause_print` custom order type in Limio.

## Cause 4: the subscription has no status

Without a rule, a subscription with no status has no actions. Check the subscription in Limio.

## Cause 5: the subscription does not meet the conditions of the action

Each action has conditions. For example, Update Subscription needs a subscription that is active and is not a gift. Change Address needs a subscription that is not a gift and has an end date in the future.

## Cause 6: your copy of the master flow is out of date

Your org uses its own copy of the Limio Manage Subscriptions flow, and an upgrade does not change it. After an upgrade, compare your copy with the packaged flow and add the new or changed action branches. See [Subflow: Update Subscription](/salesforce/servicing-subscriptions/manage-subscriptions-flow/subflow-update-subscription.md).

## Cause 7: the action list does not load

If the action list fails to load, check the input mapping of **Get Subscription Actions** in your flow. See [Subscription Actions Fail to Load](/salesforce/support/troubleshooting/failed-load-actions.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.limio.com/salesforce/support/troubleshooting/no-actions-available.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.