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

Some jobs report UNSUPPORTED_FILE_TYPE Exception but by Status is Good According to API #399

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

Originally created by @adreichert on GitHub (Jan 3, 2025).

Describe the bug
I have a directory containing several hundred HTML files. When I parse them with theload_data in the Python llama_parse package, the code fails with the UNSUPPORTED_FILE_TYPE exception.

  • Each time, it happens with different files
  • If I check the status quickly with web UI within a few seconds, I see "failed" and the error. But If I refresh the page, it lists success. The results seems correct.
  • One can also see successful job status using the API
lp = llama_parse.LlamaParse(
        api_key=lp,
        result_type='markdown',
        verbose=False,
        use_vendor_multimodal_model=True,
        vendor_multimodal_model_name='openai-gpt4o',
       [... other options..]
    )
lp.load_data(files)  <-- files is a list of paths


File ".../llama_parse/base.py", line 654, in _get_job_result
    raise Exception(exception_str)
Exception: Job ID: 3e3b9c18-8059-4c4d-bf84-a138d73e2208 failed with status: ERROR, Error code: UNSUPPORTED_FILE_TYPE, Error message: Unsupported file type.
[...]
% curl -X 'GET' \
  'https://api.cloud.llamaindex.ai/api/parsing/job/3e3b9c18-8059-4c4d-bf84-a138d73e2208' \
  -H 'accept: application/json' \
  -H "Authorization: Bearer $LLAMA_CLOUD_API_KEY"
{"id":"3e3b9c18-8059-4c4d-bf84-a138d73e2208","status":"SUCCESS"}%

Job ID
3e3b9c18-8059-4c4d-bf84-a138d73e2208

Client:
Please remove untested options:

  • Python Library
Originally created by @adreichert on GitHub (Jan 3, 2025). **Describe the bug** I have a directory containing several hundred HTML files. When I parse them with the`load_data` in the Python `llama_parse` package, the code fails with the `UNSUPPORTED_FILE_TYPE` exception. * Each time, it happens with different files * If I check the status quickly with web UI within a few seconds, I see "failed" and the error. But If I refresh the page, it lists success. The results seems correct. * One can also see successful job status using the API ``` lp = llama_parse.LlamaParse( api_key=lp, result_type='markdown', verbose=False, use_vendor_multimodal_model=True, vendor_multimodal_model_name='openai-gpt4o', [... other options..] ) lp.load_data(files) <-- files is a list of paths File ".../llama_parse/base.py", line 654, in _get_job_result raise Exception(exception_str) Exception: Job ID: 3e3b9c18-8059-4c4d-bf84-a138d73e2208 failed with status: ERROR, Error code: UNSUPPORTED_FILE_TYPE, Error message: Unsupported file type. [...] % curl -X 'GET' \ 'https://api.cloud.llamaindex.ai/api/parsing/job/3e3b9c18-8059-4c4d-bf84-a138d73e2208' \ -H 'accept: application/json' \ -H "Authorization: Bearer $LLAMA_CLOUD_API_KEY" {"id":"3e3b9c18-8059-4c4d-bf84-a138d73e2208","status":"SUCCESS"}% ``` **Job ID** 3e3b9c18-8059-4c4d-bf84-a138d73e2208 **Client:** Please remove untested options: - Python Library
yindo added the bug label 2026-02-16 00:17:43 -05:00
yindo commented 2026-02-16 00:17:44 -05:00
Author
Owner
Copy Link
Copy Source

@adreichert commented on GitHub (Jan 3, 2025):

One more thing. I parse these files a few days ago without issue. I don't believe the contents have changed, but it is possible.

@adreichert commented on GitHub (Jan 3, 2025): One more thing. I parse these files a few days ago without issue. I don't believe the contents have changed, but it is possible.
yindo commented 2026-02-16 00:17:44 -05:00
Author
Owner
Copy Link
Copy Source

@adreichert commented on GitHub (Jan 4, 2025):

The workaround was to keep retrying while relying on cached results. I ran it a few more times. Each time, a different file would cause the error and then be marked as successful. After this, the process completed.

@adreichert commented on GitHub (Jan 4, 2025): The workaround was to keep retrying while relying on cached results. I ran it a few more times. Each time, a different file would cause the error and then be marked as successful. After this, the process completed.
yindo commented 2026-02-16 00:17:44 -05:00
Author
Owner
Copy Link
Copy Source

@edanweis commented on GitHub (Jan 21, 2025):

any updates on this? I'm getting the same problem intermittently via REST api

@edanweis commented on GitHub (Jan 21, 2025): any updates on this? I'm getting the same problem intermittently via REST api
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#399
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?