#general
Sep 15September 16, 2026
hello there, I wanted to ask question related with knowledge base
• I have ingested the knowledge through the connector.
• the docs already indexed.
• The agent plug only the knowledge base because I assume docs already indexed
but when I inquiry the agent about the recent incident (which should be exist in knowledge base), it cant find anything (?)
However, if I plug the connector, the agent was able to fetch through the connector.
am I understand the concept of knowledge base correctly or I am missing something here that makes the agent unable to see the indexed docs?
I haven't checked to see if it's been changed, but is anyone aware if the SharePoint knowledge connector still grabs all pages, published and draft?
New blog post alert :speech_balloon:
We built a tool internally, that fixes Archestra bugs through autonomous sessions launched from Slack. While it works well for small fixes, it touches internal data and has ability to create PRs - basically has a full complex of Lethal Trifecta. In this post we share how we made sure this agent is secure and easy to use. Spoiler - everything starts with dropping a :crab: in Slack.
Read-only live mirror of Archestra.AI Slack
👋Join the discussion withAI enthusiasts!I haven't checked to see if it's been changed, but is anyone aware if the SharePoint knowledge connector still grabs all pages, published and draft?
8 replies
hello! currently it indexes both published and draft pages.
we will add a connector setting to allow specifying the behaviour here. this will be available in the upcoming v1.4.0-beta.10 release. stay tuned 🙂
Thanks
hello 👋 v1.4.0-beta.10 is now available - please give this a try and let me know if you have any issues
I'll check it out soon. I was looking at openappa too, looks like it's currently implementation will block all chatops sources. Doesn't look like they are in the allow list for chat sources
@user
Hi! @user, thanks for looking into it!
looks like it's currently implementation will block all chatops sources
Could you elaborate on that? Also, appa in archestra is in pre-alpha state currently, but we are always happy to get some feedback 😉
I enabled just to check it out, noticed my teams messages stopped working. I was working from my phone so haven't read much of the code myself.
Teams message came back with:
⚠️ Access Denied
OpenAPPA requires an authenticated Archestra caller
I asked Claude to clone the repo and trace back that message and didn't realise it was on opus so got some profound ted talk back. I haven't checked any of this is correct yet, as I'm on my phone
With ARCHESTRAOPENAPPAENABLED=true, ChatOps turns fail with a 401 from sessionFromHeaders() in openappa/service.ts, because llm-client.ts adds X-Appa-Session-ID but llm-proxy-handler.ts only resolves a loopback caller for sources in APPACHATSOURCES, and chatops:ms-teams isn't one. Adding it to that list won't work on its own, because the ConversationModel.getAgentIdForUser check would then 403 on the buildChatOpsSessionId session IDs, so ChatOps needs its own trusted-caller branch using the Teams-resolved user ID.
Thanks for the report