> For the complete documentation index, see [llms.txt](https://docs.aisera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisera.com/aisera-platform/content-generation-from-tickets/functionality-of-generated-documents-that-are-recrawled.md).

# Functionality of Generated Documents that are Recrawled

You can upload the document to the source system, allowing customers to review, update if needed, and send it back to the data store on your Aisera GenAI platform. During recrawl, the updated content from the source system will override the corresponding generated documents. 

The following table describes possible use cases

| **Use Cases**                                                     | **Impact when the published document is crawled back.**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
| ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Case 1:** Generated Documents Uploaded to Aisera Only           | Since the source system lacks the generated document (as it was not published to SOR but only exists in Aisera), recrawling from the source system has no impact, and no document will be overridden.                                                                                                                                                                                                                                                                                                                                                                             |
| **Case 2:** Document Exists in Both Aisera and SOR                | <p>When a document exists in both systems, any updates made in the source system and recrawled will override the corresponding document in SOR → Knowledge and the Knowledge Generation page. </p><p>To help identify Aisera-generated documents that have been recrawled, a label is provided for these documents. <br>Tabs where recrawled Aisera-generated documents are labeled: </p><p>SOR: Knowledge Details page </p><p>Content Generation: Knowledge Generation → Knowledge Details page </p><p>Content Generation: Knowledge Generation → Similar Documents </p><p> </p> |
| **Case 3:** Document Uploaded Only to SOR                         | <p>Since the generated document is stored in SOR and later crawled into Aisera, the version in the Knowledge Generation page will be overridden. However, as the document does not exist in SOR → Knowledge within Aisera, there is no further impact. </p><p>The label for recrawled Aisera-generated documents will be visible on the Generated Document page as mentioned above. </p>                                                                                                                                                                                          |
| **Case 4:** Document Exists Only in the Knowledge Generation Page | As the document has not been published, recrawling has no impact.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |

&#x20;

&#x20;

&#x20;


---

# 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://docs.aisera.com/aisera-platform/content-generation-from-tickets/functionality-of-generated-documents-that-are-recrawled.md?ask=<question>&goal=<endgoal>
```

`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.