Pega Knowledge Buddy 26 – Has anyone experienced QueueIngestion failure with "Chat with your documents"?

Hi all,

Is anyone else seeing this with the “Chat with your documents” feature in Pega Knowledge Buddy '26 on Pega Infinity '26?

Setup

We’ve completed the configuration as described in the Knowledge Buddy '26 documentation (“Completing the prerequisites to chat with your documents”):

  • Collection, Attachments data source and Case buddy created
  • The KnowledgeBuddy_OAuth_DataUser client mapped to BuddyDataSourceManager, with credentials updated in the implementation application’s authentication profile
  • KnowledgeBuddySvcURL / pyBuddySvcURL and pyBuddyDataUserAuthenticationProfile configured

The OAuth token request succeeds (200) and the Knowledge Buddy service is reached.

Issue

Content added directly in the Knowledge Buddy portal is ingested without problems. Attachments added to a case in the implementation application are never ingested.

The flow is:

  1. pzIngestAttachmentToKBAsync → pzIngestFile calls PUT /prweb/api/knowledgebuddy/v1/indexes/attachments
  2. On the Knowledge Buddy side: CreateIndexAttachment_Service → bxCreateIndexContent → Approve → stage change → Ingestion_Flow → QueueIngestion
  3. QueueIngestion step 2 (Queue-For-Processing) fails with:
    PRQueueException: Enqueue to queue processor ProcessIngestion failed (no message text, thrown from AbstractQueueProcessor.validateQueueItemPage)
  4. The API still returns 202 with an empty body, the article stays in draft, and any retry for the same attachment returns 500 DraftInProgress.

What Tracer shows

QueueIngestion step 1 calls PegaFW-KB-Work-Article.BuildContentURL (Data Transform, KnowledgeQA ruleset, availability Final). Step 4 of that rule builds the path from the Application clipboard page:

"/PRAuth/app/" + @if(Application.pyProductAlias=="", Application.pyProductName, Application.pyProductAlias) + "/km/content/"

In the REST service requestor there’s no Application page, so both values are empty and the result is:

https://<host>/prweb/PRAuth/app//km/content/KB-XXXX

After this step the article page goes from pzStatus = valid to pzStatus = false, and the enqueue to ProcessIngestion then fails because the queue item page is invalid.

In the same requestor, pxThread.pxCurrentApplicationName correctly shows KnowledgeBuddy. In the portal (interactive) path, the Application page exists and the URL is built correctly (…/PRAuth/app/KnowledgeBuddy/km/content/KB-XXXX).

What we’ve ruled out

  • Authentication: the token is issued and the service executes
  • Access: the same failure occurs with the service operator on KnowledgeBuddy:Admins, the access group that works in the portal
  • Custom rules: every rule in the failing path is in Pega’s KnowledgeQA ruleset

Questions

    1. Has anyone else run into this when ingesting case attachments through “Chat with your documents”?

    2. Is there a known fix or hotfix for BuildContentURL in service or background requestor contexts?

    3. Since BuildContentURL is Final, has anyone used a supported workaround, such as making the Application page available earlier in the service request (a requestor initialization activity on the service package, for example)?

      Any pointers would be much appreciated. Thanks!

I would recommend to create INC ticket since you’re getting HTTP 202 but the documents are NOT ingested.

Thanks @RameshSangili. I raised an SR, and with Pega Support’s help I found the root cause. I am posting it here in case it helps others.

Root cause

In the Knowledge Buddy REST API service package (knowledgebuddy, used by PUT /indexes/attachments), “Requires authentication” was unchecked. Checking it fixed the empty alias in the Content URL, and ingestion now works.

In my original post, I said authentication had been ruled out. That was wrong: the OAuth token was issued, but the service package ignored it.

Why it caused the empty alias

  • With “Requires authentication” unchecked, the request is processed as unauthenticated. The bearer token from the DataUser authentication profile is ignored, so the operator context in KnowledgeBuddy_OAuth_DataUser is never applied.
  • The request runs only with the package’s service access group. The article is created under the calling user’s identity, not the configured data user.
  • In that context, there is no Application page on the clipboard. BuildContentURL produces /PRAuth/app//km/content/ (empty alias), which gives https://<host>/prweb/PRAuth/app//km/content/KB-XXXX. The page fails validation (pyInvalidURLProvided), so QueueIngestion can’t add the item to the ProcessIngestion queue, and the case goes to FlowProblems.
  • With “Requires authentication” checked, the token is validated and the request runs in the authenticated Knowledge Buddy context. The Content URL gets the correct alias, and the item is queued.