run-llama/llama_cloud_services
1
0
Fork 0
mirror of https://github.com/run-llama/llama_cloud_services.git synced 2026-08-27 19:30:01 -04:00
Code Issues 352 Packages Projects Releases 10 Wiki Activity

Job still in progress after more than 48 hours #435

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

Originally created by @mehwishh247 on GitHub (Feb 19, 2025).

Slow results and in-progress job after 3 days
Recently, LlamaParse isn't performing well at all. Three days to be precise. Three days ago I started a job and it is still showing it in progress. Ever since, the library isn't posting the content_guideline_instructions either. The web GUI was working before but even that isn't reading any guideline or prompt. Overall the whole library/API is buggy and extremely slow at the moment

Job ID
069da5c8-fc37-4483-b341-239d4104d1dc

Client:
Please remove untested options:

  • Python Library
  • API
  • Frontend (cloud.llamaindex.ai)

Additional context
Used with all accurate and premium modes. Premium mode is extremely slow. Like 4 5 minutes
Image

Originally created by @mehwishh247 on GitHub (Feb 19, 2025). **Slow results and in-progress job after 3 days** Recently, LlamaParse isn't performing well at all. Three days to be precise. Three days ago I started a job and it is still showing it **in progress**. Ever since, the library isn't posting the content_guideline_instructions either. The web GUI was working before but even that isn't reading any guideline or prompt. Overall the whole library/API is buggy and extremely slow at the moment **Job ID** 069da5c8-fc37-4483-b341-239d4104d1dc **Client:** Please remove untested options: - Python Library - API - Frontend (cloud.llamaindex.ai) **Additional context** Used with all accurate and premium modes. Premium mode is extremely slow. Like 4 5 minutes ![Image](https://github.com/user-attachments/assets/9b2afb33-cd34-49ea-94a2-430694b52d02)
yindo added the bug label 2026-02-16 00:17:49 -05:00
yindo commented 2026-02-16 00:17:50 -05:00
Author
Owner
Copy Link
Copy Source

@qasim-mobi commented on GitHub (Feb 20, 2025):

Experiencing the same issues. It is becoming very risky to use LlamaParse in Production Environment.

@qasim-mobi commented on GitHub (Feb 20, 2025): Experiencing the same issues. It is becoming very risky to use LlamaParse in Production Environment.
yindo commented 2026-02-16 00:17:50 -05:00
Author
Owner
Copy Link
Copy Source

@DillonOLeary commented on GitHub (Jul 24, 2025):

I'm also running into this. I need a solid SLA or something otherwise I can't use LlamaCloud

@DillonOLeary commented on GitHub (Jul 24, 2025): I'm also running into this. I need a solid SLA or something otherwise I can't use LlamaCloud
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
LlamaCloud
LlamaExtract
LlamaParse
bug
client
complex layout
documentation
duplicate
enhancement
figure
font
header footer
help wanted
ocr
parser
pdf_debug
pdf_debug
pull-request
Mirrored from GitHub Pull Request
 python-lib
question
server_issue
server_issue
ui
No Label bug
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/llama_cloud_services#435
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?