run-llama/notebookllama
1
0
Fork 0
mirror of https://github.com/run-llama/notebookllama.git synced 2026-07-16 07:04:28 -04:00
Code Issues 9 Packages Projects Releases 10 Wiki Activity

[REPORT] Error processing document: Error in step 'extract_file_data': unhandled errors in a TaskGroup (1 sub-exception) #13

New Issue
Open
opened 2026-02-16 03:17:20 -05:00 by yindo · 4 comments
yindo commented 2026-02-16 03:17:20 -05:00
Owner
Copy Link
Copy Source

Originally created by @jingyi-zhao-01 on GitHub (Oct 2, 2025).

Originally assigned to: @AstraBert on GitHub.

Checklist

Before reporting bugs or help requests, please fill out the following checklist:

  • I set the .env file with the necessary keys, including OPENAI_API_KEY, LLAMACLOUD_API_KEY, ELEVENLABS_API_KEY
  • My API keys are all functioning and have at least some credit balance
  • I ran both the scripts in the tools directory
  • I checked that my LlamaCloud Extract Agent and my LlamaCloud Index has been correctly created and are functioning (using the playground functionality in the UI
  • I activated the virtual environment and ensured that all the dependencies are installed properly
  • As a first step, I launched the docker services through docker compose up -d
  • As a second step, I launched the MCP server through uv run src/notebookllama/server.py
  • As a third and last step, I launched the Streamlit app through strealit run src/notebookllama/Home.py

Issue Description

My issue is...

Image

Relevant Traceback

i noticed this problem is only present when parsing large PDF, for small PDF this is fine

Other details

OS:
OS: Arch Linux x86_64
Kernel: 6.16.1-arch1-1
Uptime: 3 days, 22 hours, 18 mins
Packages: 1368 (pacman), 10 (flatpak)
Shell: zsh 5.9
Resolution: 3840x2160
DE: Hyprland
WM: sway
Theme: Raleigh [GTK2/3]
Icons: breeze-dark [GTK2/3]
Terminal: kitty
CPU: AMD Ryzen 7 3700X (16) @ 3.600GHz
GPU: AMD ATI Radeon RX 5600 OEM/5600 XT / 5700/5700 XT
Memory: 19790MiB / 64197MiB

uv version:
0.8.22
streamlit version:
1.46.1
fastmcp version:
FastMCP version: 2.9.2
MCP version: 1.9.4
Python version: 3.13.7
Platform: Linux-6.16.1-arch1-1-x86_64-with-glibc2.42
FastMCP root path: /home/jingyi/PycharmProjects/notebookllama/.venv/lib/p…
llama-index-workflows version:
1.0.1

Originally created by @jingyi-zhao-01 on GitHub (Oct 2, 2025). Originally assigned to: @AstraBert on GitHub. ### Checklist Before reporting bugs or help requests, please fill out the following checklist: - [X] I set the `.env` file with the necessary keys, including OPENAI_API_KEY, LLAMACLOUD_API_KEY, ELEVENLABS_API_KEY - [X] My API keys are all functioning and have at least some credit balance - [X] I ran both the scripts in the `tools` directory - [X] I checked that my LlamaCloud Extract Agent and my LlamaCloud Index has been correctly created and are functioning (using the playground functionality in the [UI](https://cloud.llamaindex.ai) - [X] I activated the virtual environment and ensured that all the dependencies are installed properly - [X] As a first step, I launched the docker services through `docker compose up -d` - [X] As a second step, I launched the MCP server through `uv run src/notebookllama/server.py` - [X] As a third and last step, I launched the Streamlit app through `strealit run src/notebookllama/Home.py` ### Issue Description My issue is... <img width="3268" height="888" alt="Image" src="https://github.com/user-attachments/assets/1189b31d-cfc5-4c20-90d9-d563f9590496" /> ### Relevant Traceback ```text i noticed this problem is only present when parsing large PDF, for small PDF this is fine ``` ### Other details **OS**: OS: Arch Linux x86_64 Kernel: 6.16.1-arch1-1 Uptime: 3 days, 22 hours, 18 mins Packages: 1368 (pacman), 10 (flatpak) Shell: zsh 5.9 Resolution: 3840x2160 DE: Hyprland WM: sway Theme: Raleigh [GTK2/3] Icons: breeze-dark [GTK2/3] Terminal: kitty CPU: AMD Ryzen 7 3700X (16) @ 3.600GHz GPU: AMD ATI Radeon RX 5600 OEM/5600 XT / 5700/5700 XT Memory: 19790MiB / 64197MiB **uv version**: 0.8.22 **streamlit version**: 1.46.1 **fastmcp version**: FastMCP version: 2.9.2 MCP version: 1.9.4 Python version: 3.13.7 Platform: Linux-6.16.1-arch1-1-x86_64-with-glibc2.42 FastMCP root path: /home/jingyi/PycharmProjects/notebookllama/.venv/lib/p… **llama-index-workflows version**: 1.0.1
yindo added the bughelp wanted labels 2026-02-16 03:17:20 -05:00
yindo commented 2026-02-16 03:17:20 -05:00
Author
Owner
Copy Link
Copy Source

@jingyi-zhao-01 commented on GitHub (Oct 2, 2025):

i noticed there is an issue opened before but for windows, is the fix specific for windows environment ?

@jingyi-zhao-01 commented on GitHub (Oct 2, 2025): i noticed there is an issue opened before but for windows, is the fix specific for windows environment ?
yindo commented 2026-02-16 03:17:20 -05:00
Author
Owner
Copy Link
Copy Source

@AstraBert commented on GitHub (Oct 2, 2025):

No, this is mostly a timeout issue with the communication between LlamaCloud and MCP: since we wait for the extraction job to be completed, but some job take longer than other (big PDFs, as you were saying), it tends to happen that it times out on longer jobs (I think longer than 5 or 10 minutes, I don't remember how long we set the timer to be).
There is no real workaround for this except for raising the timeout threshold of the MCP

@AstraBert commented on GitHub (Oct 2, 2025): No, this is mostly a timeout issue with the communication between LlamaCloud and MCP: since we wait for the extraction job to be completed, but some job take longer than other (big PDFs, as you were saying), it tends to happen that it times out on longer jobs (I think longer than 5 or 10 minutes, I don't remember how long we set the timer to be). There is no real workaround for this except for raising the timeout threshold of the MCP
yindo commented 2026-02-16 03:17:20 -05:00
Author
Owner
Copy Link
Copy Source

@jingyi-zhao-01 commented on GitHub (Oct 2, 2025):

got it, thanks for the reply, is there any configs we can modify to adjust the fastMCP timeout

@jingyi-zhao-01 commented on GitHub (Oct 2, 2025): got it, thanks for the reply, is there any configs we can modify to adjust the fastMCP timeout
yindo commented 2026-02-16 03:17:20 -05:00
Author
Owner
Copy Link
Copy Source

@AstraBert commented on GitHub (Oct 24, 2025):

Yes, you can change this line: https://github.com/run-llama/notebookllama/blob/fbae0294329853932e19cf1be10885a81a1e2cd5/src/notebookllama/workflow.py#L9 to put the timeout to a higher limit

@AstraBert commented on GitHub (Oct 24, 2025): Yes, you can change this line: https://github.com/run-llama/notebookllama/blob/fbae0294329853932e19cf1be10885a81a1e2cd5/src/notebookllama/workflow.py#L9 to put the timeout to a higher limit
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
enhancement
help wanted
help wanted
pull-request
Mirrored from GitHub Pull Request
 triage
No Label bug help wanted
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/notebookllama#13
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?