1. What is this screen for?

The Ingestion Log shows every attempt to process a document into an agent's knowledge base, with details on what succeeded and what failed. By default, it is filtered to show only failures.

2. Who uses it?

Administrators at your organization.

3. What do you actually do here?

The log is a table with these columns:

Started — the date and time the ingestion attempt began.

Type — the kind of operation (e.g., "Ingest").

Agent Instance — which agent the document was being added to.

Document — the file that was being processed.

Status — the result of the ingestion job. Possible values: Running (in progress), Succeeded (completed successfully) and Failed (did not complete). Each new attempt at a file gets its own row. A red Failed badge means the document was not processed.

Error — a description of what went wrong (e.g., "Timed out — no result callback received").

The search bar has the Failed filter active by default. Remove it to see all ingestion attempts, including successful ones.

This screen is read-only — you cannot retry or fix anything from here. It tells you what failed and why, so you know what to do next.

4. What do you do when it looks wrong or empty?

Log shows failed entries: Read the Error column: it says what went wrong and what to do. "Timed out — no result callback received" means no answer came back at all; it appears 30 to 45 minutes after the attempt started. To try again, add the file again with Add Documents. There is no need to remove it first.

There is no stated file-size limit for ingestion. However, a PDF that is not converted within about fifteen minutes, counting time spent waiting behind other files, fails with "The file was not converted in time because document processing was busy"; add it again later. So the practical limit is processing time rather than an enforced cap.

Same document fails multiple times: Each attempt creates a new log entry, whether you add the file again or a tag subscription retries it (tag retries stop after five failures in a row). If the error says processing was busy, add it again later. Otherwise the file itself is likely the problem — try a different version, or contact help@wiz.asia quoting the reference in the error.

Log is empty (with Failed filter active): This is good — no ingestion failures have occurred. Remove the filter to confirm that successful ingestions are being logged normally.

Files added with Add Documents are sent for processing as soon as you click Add & Ingest. Tag subscriptions also re-sync every thirty minutes, and immediately when you save the tag.