Our org seems to be having issues with having things populate from Atlassian in Glean. Has anyone else ran into this and know what options are?
Yes - we started noticing that many Confluence pages are not indexed a few days ago. I submitted a support ticket and support shared a document with me about a known issue. It is really important that we all open tickets with Atlassian to put pressure on them. Without Confluence being fully indexed, our instance of Glean becomes much much less useful.
Our Sr. Dir of IT just opened a ticket with Atlassian about the rate limiting issue.
From Glean Support: I have just received confirmation that the delay is indeed related to the recent rate-limit change by Atlassian.
Engineering is currently working hard to find a solution and has shared this document for additional context in the meantime.
One thing that could potentially expedite a resolution is if your team could contact Atlassian directly and ask if it would be possible to get the confluence rate limit restored to something closer to previous values.
DOCUMENT CONTENTS
[External] Glean<> Confluence Cloud rate limits
May 16, 2025
The Glean Confluence connector relies on Forge Apps to connect to Confluence and crawl data via REST API calls using the Forge App token.
Atlassian has recently implemented significant rate limiting for Forge Apps (around 320-400 requests per hour, or ~0.1 per second), severely impacting Confluence crawls and the freshness of indexed documents.
Feel free to contact glean support(support.glean.com) for any clarifications.
