> For the complete documentation index, see [llms.txt](https://docs.marketingtool.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.marketingtool.pro/product/troubleshooting.md).

# Troubleshooting

Fixes for the most common issues

<details>

<summary>I didn't receive my sign-in code</summary>

Check your spam folder, then request a new code — codes expire after a few minutes. Corporate mail filters can delay delivery; a personal address is a quick workaround.

</details>

<details>

<summary>A tool result failed or looks incomplete</summary>

Re-run the tool — transient failures are automatically retried on our side, but a fresh run is the fastest fix. Failed runs are not meant to consume your credits; if you believe you were charged for a failure, contact support with the tool name and time.

</details>

<details>

<summary>The app can't reach the server</summary>

Check your connection, then force-close and reopen the app. If the problem persists, check the web app at [app.marketingtool.pro](https://app.marketingtool.pro/) — if the web works, reinstalling the app usually resolves it.

</details>

<details>

<summary>My subscription isn't recognized</summary>

Make sure you're signed in with the same account you subscribed with. iOS: **Settings → Subscriptions**; Android: **Play Store → Payments & subscriptions** to confirm the subscription is active, then reopen the app.

</details>

<details>

<summary>Something else?</summary>

Email <Help@marketingtool.pro> with your account email, platform (web / iOS / Android), and a screenshot if you can.

</details>


---

# 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.marketingtool.pro/product/troubleshooting.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.