# What to do if a scan is taking too long.

A Flensh scan is an incredibly intensive, real-time process. It's not just checking a few meta tags; it's performing a live, deep analysis of your content and your competitors.

**Why it takes time:**

* **Real-Time Competitor Research:** Flensh is actively searching the web to identify and analyze your top 10 competitors at the moment of your scan.
* **Multi-Engine Analysis:** Your website is being processed by multiple large language models (LLMs) to gauge its performance across different AI platforms.
* **Deep Content Assessment:** The system reads and scores your content for quality, structure, authority, and answerability.

A standard scan can take **several minutes** to complete.

**What to do:**

1. **Be Patient:** The most important step is to wait. Please allow at least 3-5 minutes for the analysis to run. Do not close the browser window immediately if it seems slow.
2. **Check Your Dashboard:** If the scan seems stuck, you can navigate back to your main dashboard in a new browser tab. Often, the scan will complete in the background, and you will see the new website card appear on your dashboard once it's finished.
3. **Contact Support:** If you have been waiting for more than 10 minutes and the scan has not completed or failed with an error, please contact our support team. Provide the URL of the website you were trying to scan so we can investigate the issue for you.


---

# 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://flensh.gitbook.io/flensh-docs/troubleshooting-and-faq/5.1.-common-scan-issues/what-to-do-if-a-scan-is-taking-too-long..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.