Viewing ingestion activity

note

Knowledge Hub is an Early Access release. Refer to the Early Access disclaimer for details.

The Sources tab shows the ingestion status for each Source in the current Knowledge Base. The Last Ingestion and Error Summary columns let you see at a glance whether ingestion succeeded or failed, and what caused a failure.

Reading ingestion status on the Sources tab

Column	What to look for
Last Ingestion	A green checkmark indicates the last run succeeded. An error icon indicates the last run failed. The timestamp shows when the run completed.
Error Summary	Shows a brief error description when the last run failed. No content appears when the last run succeeded.
Data Provider	Select the Boomi Data Integration link to open the corresponding flow in Data Integration for detailed run history and connector-level diagnostics.

Select Refresh Table to update the Sources tab with the latest ingestion status.

Investigating a failed ingestion

When the Last Ingestion column shows an error icon:

Read the Error Summary column for a brief description of the failure.
Select the Data Provider link to open the flow in Data Integration.
In Data Integration, review the execution log for the failed run. The execution log shows connector-level error details, including authentication failures, network timeouts, and schema mismatches.

note

You must have Data Integration access to follow the Data Provider link.

Common failure causes

Error	Likely cause	Resolution
Credential expired	Source connector credentials have rotated or expired.	Update the connector connection in Data Integration and redeploy the flow.
Schema mismatch	A source table or object schema changed after the flow was configured.	Review the schema mapping in the S2T flow and redeploy. Refer to the Knowledge Hub target topic in the Data Integration documentation.
Knowledge Base unavailable	The target Knowledge Base was disabled during the run.	Re-enable the Knowledge Base and trigger a manual run.
Chunk size exceeded	An individual source record exceeds the maximum embeddable token count after chunking.	Reduce chunk size in data preparation settings or exclude the oversized records using a custom query.