The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

JSM Virtual Service Agent only indexes 1 of 4 linked Confluence articles

Takemaru Hirai
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 6, 2026

Hi everyone,

I'm having an issue with AI Answers in JSM Cloud's Virtual Service Agent (VSA).

Although a linked Confluence KB space contains 4 published articles, the AI Answers setup screen shows only "1 article," and the portal chat fails to answer KB-based questions. However, all 4 articles appear properly in the standard Customer Portal search bar, suggesting the JSM-Confluence linkage works, but the AI indexing pipeline is stuck.

 

2026-09-07_14h53_04.png

1. Environment & Symptoms

  • Environment: JSM Cloud / Confluence Cloud

  • Structure: Standard Confluence space (1 home page + 2 parent pages + 4 child articles)

  • Symptoms:

    • Project settings > Virtual Service Agent > AI Answers shows "1 article".

    • Portal chat returns fallback responses ("I'm still learning") for relevant queries.

    • Standard portal search finds and displays all 4 articles normally.

2. Troubleshooting Already Attempted

  • Page Hierarchy: Verified articles are standard child pages, not Confluence Folders.

  • Re-triggering: Edited and republished each article to trigger update events.

  • Permissions: Access is set to "All logged-in users" with no page restrictions or label filters.

  • Resetting: Unlinked/re-linked the KB space and toggled AI Answers off and on.

  • Time: Waited several days with no change.

3. Questions

  1. Why would articles be visible in standard portal search but skipped by AI Answers indexing?

  2. Is there a way to force a manual rescan/sync for the Atlassian Intelligence vector index?

  3. Are there specific admin.atlassian.com settings (e.g., Rovo / Atlassian Intelligence permissions) required for AI Answers to process KB content?

Thanks in advance for your help!

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Mia Tamm _Simpleasyty_
Atlassian Partner
September 7, 2026

Since normal portal search can see all four articles, I’d separate KB visibility from AI Answers indexing.

I’d compare the one article that gets indexed with the other three — restrictions, page status, language, anything unusual at page level. If they’re genuinely identical from an access point of view, the “1 article” count is probably the most useful piece of evidence to take to support rather than rebuilding the KB again.

Takemaru Hirai
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 8, 2026

Hi Mia,

Thank you for the advice!
You were spot on about checking the "language".

I believe I have resolved this. Although the AI Answers setup screen still shows "1 article," the VSA is now successfully hitting multiple KB articles in its responses.

What I changed:
I checked the global index language settings in Confluence and found it was set to "English." Since our KB articles are in Japanese, this mismatch was the root cause. Changing the index language to "Custom Japanese" resolved the issue. Thanks so much for pointing me in the right direction!

Reference: Activate or deactivate AI answers in the virtual agent

Like Mia Tamm _Simpleasyty_ likes this
Mia Tamm _Simpleasyty_
Atlassian Partner
September 8, 2026

Hi @Takemaru Hirai glad that was it — and thanks for coming back with the root cause. The “1 article” counter still being stale is a useful detail too; that could easily send someone debugging in the wrong direction.

Nice catch on the Japanese index setting.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events