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

Getting consistent "HTTP 429 Too Many Requests" for LlamaParse API #520

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

Originally created by @milap-giantanalytics on GitHub (Aug 11, 2025).

Describe the bug
Getting consistent "HTTP 429 Too Many Requests" errors immediately when submitting documents to LlamaParse API, even with only a single document and no concurrent requests. The rate limiting appears to be overly aggressive, preventing normal usage of the service. Errors occur within 3-4 seconds of request submission, suggesting the rate limit is being triggered before any actual processing begins.

Client:

  • Python Library

Additional context
Client configuration used:

LlamaParse(
    api_key=api_key,
    result_type="text",
    preprocess_text=True,
    extract_charts=True,
    premium_mode=True,
)

Error pattern observed:

06:30:06 - HTTP 429 Too Many Requests (retry in 4.0s)
06:30:10 - HTTP 429 Too Many Requests (retry in 4.0s)  
06:30:15 - HTTP 429 Too Many Requests (retry in 4.0s)
06:30:19 - HTTP 429 Too Many Requests (retry in 8.0s)

There is nothing in the LlamaCloud dashboard to indicate if I have exceeded the API rate allowance

Originally created by @milap-giantanalytics on GitHub (Aug 11, 2025). **Describe the bug** Getting consistent "HTTP 429 Too Many Requests" errors immediately when submitting documents to LlamaParse API, even with only a single document and no concurrent requests. The rate limiting appears to be overly aggressive, preventing normal usage of the service. Errors occur within 3-4 seconds of request submission, suggesting the rate limit is being triggered before any actual processing begins. **Client:** - Python Library **Additional context** Client configuration used: ``` LlamaParse( api_key=api_key, result_type="text", preprocess_text=True, extract_charts=True, premium_mode=True, ) ``` Error pattern observed: ``` 06:30:06 - HTTP 429 Too Many Requests (retry in 4.0s) 06:30:10 - HTTP 429 Too Many Requests (retry in 4.0s) 06:30:15 - HTTP 429 Too Many Requests (retry in 4.0s) 06:30:19 - HTTP 429 Too Many Requests (retry in 8.0s) ``` There is nothing in the LlamaCloud dashboard to indicate if I have exceeded the API rate allowance
yindo added the bug label 2026-02-16 00:18:07 -05:00
yindo commented 2026-02-16 00:18:07 -05:00
Author
Owner
Copy Link
Copy Source

@logan-markewich commented on GitHub (Aug 11, 2025):

Do you have a project and/or org id that your API key is under? Would help in tracking down the requests

@logan-markewich commented on GitHub (Aug 11, 2025): Do you have a project and/or org id that your API key is under? Would help in tracking down the requests
yindo commented 2026-02-16 00:18:07 -05:00
Author
Owner
Copy Link
Copy Source

@milap-giantanalytics commented on GitHub (Aug 11, 2025):

sure, here's:

  • org id - vefe9ac22-5d86-4f23-bf22-15f1eeef292a
  • project - Default
@milap-giantanalytics commented on GitHub (Aug 11, 2025): sure, here's: * org id - `vefe9ac22-5d86-4f23-bf22-15f1eeef292a` * project - `Default`
yindo commented 2026-02-16 00:18:07 -05:00
Author
Owner
Copy Link
Copy Source

@milap-giantanalytics commented on GitHub (Aug 13, 2025):

@logan-markewich, is there an SLA timeline for such requests? Our entire pipeline is blocked because llama parsing won't work

@milap-giantanalytics commented on GitHub (Aug 13, 2025): @logan-markewich, is there an SLA timeline for such requests? Our entire pipeline is blocked because llama parsing won't work
yindo commented 2026-02-16 00:18:07 -05:00
Author
Owner
Copy Link
Copy Source

@josh-cooper commented on GitHub (Aug 27, 2025):

Same issue here

@josh-cooper commented on GitHub (Aug 27, 2025): Same issue here
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#520
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?