# Operation Manager

Operation Manager is an important component of Karsa Labelizer that provides you with an overview of the status and progress of key operations performed by the system in the background. Its main use for you as a user will primarily be in monitoring the process of creating new clusterizations.

## What is Operation Manager For?

* **Monitoring operation status:** The main function of Operation Manager is to display the current status of long-running operations, typically the clusterization process that you launched from [Cluster Designer](/iii.-cluster-designer-creating-clusterization/iii.-cluster-designer-creating-clusterization.md).
* **Process transparency:** It gives you confidence that the system is working and allows you to estimate when the operation will be completed.
* **Diagnostics (if needed):** If there were to be an issue with completing an operation, information from Operation Manager can be useful for our support team in troubleshooting.

## How Does Operation Manager Work in the Context of Clusterization?

1. **Launching clusterization:** After you configure and launch the creation of a new clusterization in [Cluster Designer](https://github.com/MJezek6/Labelizer-KB-EN/blob/Main/cluster-designer/launch-and-monitoring.md), Karsa Labelizer initiates a complex computational task in the background.
2. **Data export to GMC (manual and automatic):** For clusterizations in 'Run' status, Karsa Labelizer ensures **automatic daily export** of the supplementary XML feed to Google Merchant Center (GMC). This feed is generated to the URL set in the 'Setup' section. Additionally, Operation Manager may offer the option of **manually triggering an export**. This is useful if, for example, you've just switched a new clusterization to production status and want to generate an XML feed immediately without waiting for the regular automatic update.
3. **Display in Operation Manager:** This running task (clusterization operation) appears in Operation Manager. You should see at minimum:
   * Operation identification (OperationType).
   * Current status (e.g., "Running", "Analysis in progress", "Completed", "Error").
   * Possibly the start time or estimated completion time.
4. **Clusterization duration:** As mentioned in [Service Lifecycle](/ii.-first-steps/service-lifecycle.md), the clusterization process itself usually takes **2 to 15 minutes**, depending on the volume of data and complexity. During this time, you can monitor its progress in Operation Manager.
5. **Operation completion:** After successful completion of the operation, the status in Operation Manager is updated (e.g., to "Completed") and the newly created clusterization appears in your category structure, ready for [analysis](/iv.-analysis-and-optimization/iv.-analysis-and-optimization.md).

## Where Can I Find Operation Manager?

You can find Operation Manager in the 'Tools' tab under the 'Operation manager' item.

***

For most users, Operation Manager will primarily serve as an information panel to confirm that a launched clusterization is proceeding as expected. Detailed technical logs are usually not displayed here, but it provides peace of mind and an overview of background processes.


---

# 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://doc.karsa.ai/ii.-first-steps/operation-manager.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.