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

LlamaParse through TS failing with unclear error log #519

New Issue
Closed
opened 2026-02-16 00:18:06 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 00:18:06 -05:00
Owner
Copy Link
Copy Source

Originally created by @clrt1 on GitHub (Aug 11, 2025).

Describe the bug
Since August 7th, my usage of LlamaParseReader.loaddata has been failing with the following error logging: "Error while parsing the file with: [object Object]". It was working fine up until that date and has been failing constantly since. Personally, I cannot find the issue in the changes merged around that date.

The unclear error logging appears right after the log "Started uploading the file", so I don't even get a job ID. My usage credits and API key do not indicate a permission or limit issue.

Client:
Please remove untested options:

  • Typescript Library

Additional context
My options used (same as before August 7th):
resultType: "markdown", // Options: "text", "markdown", "json"
maxTimeout: 3600, // 1 hour in seconds
verbose: true, // Detailed progress logs from LlamaParse
ignoreErrors: true, // Whether to ignore errors from LlamaParse (get empty array instead)
language: language, // Language of the document (default: "en")
skipDiagonalText: false, // Whether to skip diagonal text (default: false)
doNotCache: false, // Whether to not cache the result (default: false)
fastMode: false, // Whether to use fast mode (default: false)
splitByPage: true, // Whether to create one document per page (default: true)
useVendorMultimodalModel: false

Originally created by @clrt1 on GitHub (Aug 11, 2025). **Describe the bug** Since August 7th, my usage of LlamaParseReader.loaddata has been failing with the following error logging: "Error while parsing the file with: [object Object]". It was working fine up until that date and has been failing constantly since. Personally, I cannot find the issue in the changes merged around that date. The unclear error logging appears right after the log "Started uploading the file", so I don't even get a job ID. My usage credits and API key do not indicate a permission or limit issue. **Client:** Please remove untested options: - Typescript Library **Additional context** My options used (same as before August 7th): resultType: "markdown", // Options: "text", "markdown", "json" maxTimeout: 3600, // 1 hour in seconds verbose: true, // Detailed progress logs from LlamaParse ignoreErrors: true, // Whether to ignore errors from LlamaParse (get empty array instead) language: language, // Language of the document (default: "en") skipDiagonalText: false, // Whether to skip diagonal text (default: false) doNotCache: false, // Whether to not cache the result (default: false) fastMode: false, // Whether to use fast mode (default: false) splitByPage: true, // Whether to create one document per page (default: true) useVendorMultimodalModel: false
yindo added the bug label 2026-02-16 00:18:06 -05:00
yindo closed this issue 2026-02-16 00:18:06 -05:00
yindo commented 2026-02-16 00:18:06 -05:00
Author
Owner
Copy Link
Copy Source

@clrt1 commented on GitHub (Aug 25, 2025):

Apologies, it was in fact a minor bug on my end. Thanks all for your great work and best wishes!

@clrt1 commented on GitHub (Aug 25, 2025): Apologies, it was in fact a minor bug on my end. Thanks all for your great work and best wishes!
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#519
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?