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

Error while parsing the file #182

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

Originally created by @Hicham-e on GitHub (Jul 11, 2024).

Originally assigned to: @hexapode on GitHub.

i have been working with llamaparse for quite a while and never got this error until now.
some documents get parsed without problems, and others get this error (Error while parsing the file 'file path' : 'markdown') even though i was working with the same documents before and never had problems with it.
I even went llamaCloud and uploaded the documents there to test and still the same problem with the same documents i get this error (Result not found. Check job status to see if it has completed.)
here's one of those files if you want to test it:
test.pdf

Originally created by @Hicham-e on GitHub (Jul 11, 2024). Originally assigned to: @hexapode on GitHub. i have been working with llamaparse for quite a while and never got this error until now. some documents get parsed without problems, and others get this error (Error while parsing the file 'file path' : 'markdown') even though i was working with the same documents before and never had problems with it. I even went llamaCloud and uploaded the documents there to test and still the same problem with the same documents i get this error (Result not found. Check job status to see if it has completed.) here's one of those files if you want to test it: [test.pdf](https://github.com/user-attachments/files/16180789/test.pdf)
yindo closed this issue 2026-02-16 00:17:04 -05:00
yindo commented 2026-02-16 00:17:04 -05:00
Author
Owner
Copy Link
Copy Source

@hexapode commented on GitHub (Jul 12, 2024):

Thansk for repporting!

Seems to have been a cache issue, for some reason the initial job parsing failed, and the error result were cached.

I re-run the job with invalidate_cache=true and the result came back as expected on this document.

In a future release (next week) we will make sure to handle this corner case so it never happen again

@hexapode commented on GitHub (Jul 12, 2024): Thansk for repporting! Seems to have been a cache issue, for some reason the initial job parsing failed, and the error result were cached. I re-run the job with `invalidate_cache=true` and the result came back as expected on this document. In a future release (next week) we will make sure to handle this corner case so it never happen again
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
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#182
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?