It seems the index configuration was completed at the metadata level, but the underlying chunk table was never physically created or materialised.
Try below -
Delete and recreate the Search Index rather than querying the chunk table directly. The chunk DMO isn’t meant to be hand-queried in Data Explorer as your primary check anyway, recreating forces the chunk table to rebuild. Confirm the source DMO has rows first.
Verify the source DMO (KnowledgeArticleVersion__dlm) is populated and mapped before rebuilding. No source content, no chunk table.
Since this is a vector/Search Index feature that’s still maturing in Data Cloud, if the source has data and a clean rebuild still leaves the chunk table missing, treat it as a platform provisioning issue and raise a case with the TraceId from your error (33aa86a19608e2b0). That TraceId lets Salesforce pull the exact failure in the chunking/embedding job server-side, which is the one thing none of us can see from the UI, the Ready status is hiding whatever actually failed underneath.
1 réponse
