> For the complete documentation index, see [llms.txt](https://doc.karsa.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.karsa.ai/iii.-cluster-designer-creating-clusterization/launch-and-monitoring.md).
# Launch and Monitoring
After carefully configuring all parameters of your new clusterization in the **Cluster Designer** – from [basic settings](/iii.-cluster-designer-creating-clusterization/creating-new-clusterization.md), through [limits and goals](/iii.-cluster-designer-creating-clusterization/setting-limits-and-goals.md), [parameter selection](/iii.-cluster-designer-creating-clusterization/parameter-selection.md), [Custom Label setup](/iii.-cluster-designer-creating-clusterization/custom-label-setup.md), to [product dynamics management](/iii.-cluster-designer-creating-clusterization/product-dynamics-management.md) – you are ready to start the actual process of creating clusters.
## 1. Launching the Clusterization Process
* **Final check:** Before starting the process, we recommend quickly going through all settings once more to make sure they match your intention.
* **Launch button:** In the Cluster Designer interface, you will find a button designed to start the clusterization operation (Arrow icon).
* **What happens after clicking:** After clicking this button, Karsa Labelizer sends your configuration and product data for processing by its AI algorithms. In the background, a complex computational task begins that analyzes the data and creates optimal grouping of products into clusters.
## 2. Monitoring the Operation Progress
Once the clusterization process is launched, it is important to be able to monitor its status and progress.
* **Operation Manager:** You can monitor the progress of this computationally intensive operation in the [Operation Manager](/ii.-first-steps/operation-manager.md) module. Here you should see your newly launched task and its current status.
* **Expected duration:** The actual calculation and creation of clusters usually takes **2 to 15 minutes**. The exact time depends on several factors:
* **Number of products:** A larger number of products naturally requires more processing time.
* **Data distribution:** The complexity and variability of your product data can affect the computational intensity.
* **Number of cluster combinations explored:** Depending on the set limits and chosen parameters, the AI may search through a varying size of possible solution space.
## 3. What Happens After Completion?
* **Creation of a new clusterization category:** After successful completion of the process, Karsa Labelizer automatically creates a new **category** in your structure that bears the name of your clusterization. Inside this category, you will find the individual generated **clusters** as its subcategories. These clusters represent specific groups of products ready for analysis and subsequent use in your campaigns.
* **Ready for analysis:** Your new clusterization is now ready for detailed exploration using reports in the [IV. Analysis and Optimization](/iv.-analysis-and-optimization/iv.-analysis-and-optimization.md) section. You can check metrics such as `Consistency`, look at the characteristics of individual clusters, and the products they contain.
* **Transition to production:** If you are satisfied with the resulting design, you can switch the clusterization to [production mode (`ProductionRun`)](https://github.com/MJezek6/Labelizer-KB-EN/blob/Main/v.-deployment-and-strategy/production-deployment.md) to start generating Custom Labels into Google Merchant Center and possibly activate dynamic product movements.
***
Launching the clusterization is the culmination of your configuration work in the Cluster Designer. Thanks to monitoring in the Operation Manager, you have an overview of what is happening, and after completion, you can smoothly move on to analyzing the results. This step completes the configuration within the Cluster Designer section.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://doc.karsa.ai/iii.-cluster-designer-creating-clusterization/launch-and-monitoring.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.