> For the complete documentation index, see [llms.txt](https://help.chatlyai.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.chatlyai.app/frequently-asked-questions/subscription/subscription-issues.md).

# Subscription Issues

### I have upgraded the subscription to a Premium version, and now it is requesting that I purchase it again.

To assist you in resolving this issue as quickly as possible.

* Please log in to your account and open your profile menu at the bottom of your left sidebar > **Settings** > **Plan & Billing**. Check if any subscription is currently active.
* Ensure the payment for the Premium version upgrade was successfully processed. You can check your email inbox or spam folder for a payment confirmation receipt.
* Clear your browser cache or try accessing your account from a different browser to see if the issue persists.

If you’ve tried these steps and the issue isn’t resolved, please share the following details on support email [**support@chatlyai.app**](mailto:support@chatlyai.app)

* The email address associated with your account.
* Your payment confirmation details (like invoice).

We’ll investigate the issue promptly and ensure your Premium subscription is activated without delay.


---

# 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://help.chatlyai.app/frequently-asked-questions/subscription/subscription-issues.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.