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:
- pzIngestAttachmentToKBAsync → pzIngestFile calls
PUT /prweb/api/knowledgebuddy/v1/indexes/attachments - On the Knowledge Buddy side: CreateIndexAttachment_Service → bxCreateIndexContent → Approve → stage change → Ingestion_Flow → QueueIngestion
- QueueIngestion step 2 (Queue-For-Processing) fails with:
PRQueueException: Enqueue to queue processor ProcessIngestion failed(no message text, thrown from AbstractQueueProcessor.validateQueueItemPage) - 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
-
-
Has anyone else run into this when ingesting case attachments through “Chat with your documents”?
-
Is there a known fix or hotfix for BuildContentURL in service or background requestor contexts?
-
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!
-