microsoft / microsoft/work-iq

Bug: Unable to get contents of Loop page

Open
#42 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PowerShell
Stars
1k
Forks
132
Avg merge
5d 19h
Merged PRs (30d)
6

Description

It looks like work_iq is unable to actually see the contents of a Loop page. When asking a query like What is the earliest and latest entry in Weekly Update Loop page, I get a response which includes the following snippet:

I looked across all your enterprise data for Weekly Update Loop entries and found the shared Loop page:

Weekly Update.page (OneNote/Loop page)

The file is stored in SharePoint and appears to contain reverse‑chronological weekly updates, beginning with the January 27, 2026 entry.    

However — your organization’s search results only return a snippet of the January 27 update, and no earlier content (e.g., January 20, January 13, etc.) is included anywhere in file preview or in any other files, chats, or emails.  
🔍 What I found       
The only visible entry in the returned document is:

The response seems to imply that the MCP server is only able to see preview of the search results, and is not actually able to access the contents of the files themselves?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported query, “What is the earliest and latest entry in Weekly Update Loop page,” and compare the returned search preview with the Loop page contents. Trace the MCP server’s search and file-content retrieval path; done means the query can access the page’s entries beyond the January 27 snippet and identify the earliest and latest entries.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.