run-llama/llama_cloud_services
1
0
Fork 0
mirror of https://github.com/run-llama/llama_cloud_services.git synced 2026-07-18 15:54:38 -04:00
Code Issues 352 Packages Projects Releases 10 Wiki Activity

Error jobs with UNSUPPORTED_FILE_TYPE do not appear in the history #316

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

Originally created by @cmenge on GitHub (Nov 2, 2024).

Originally assigned to: @BinaryBrain on GitHub.

Describe the bug
When uploading a .doc and triggering an UNSUPPORTED_FILE_TYPE error via API, the corresponding job is not displayed in the history tab in the UI. However, this very bug template says, under Job ID:

You can find it here: https://cloud.llamaindex.ai/parse in the "History" tab.

Job ID
def8b8ba-e3b4-412d-b9a5-4db804a09a59

Client:

  • API
Originally created by @cmenge on GitHub (Nov 2, 2024). Originally assigned to: @BinaryBrain on GitHub. **Describe the bug** When uploading a .doc and triggering an UNSUPPORTED_FILE_TYPE error via API, the corresponding job is not displayed in the history tab in the UI. However, this very bug template says, under Job ID: > You can find it here: https://cloud.llamaindex.ai/parse in the "History" tab. **Job ID** def8b8ba-e3b4-412d-b9a5-4db804a09a59 **Client:** - API
yindo added the bug label 2026-02-16 00:17:27 -05:00
yindo closed this issue 2026-02-16 00:17:27 -05:00
yindo commented 2026-02-16 00:17:27 -05:00
Author
Owner
Copy Link
Copy Source

@BinaryBrain commented on GitHub (Nov 8, 2024):

Hi Chris,
For this job, I see the filename as: originalFileName: 'example.pdf'.
Please make sure you're sending a filename with the correct extension when calling the API.
If you send the snippet of your code, I can help you figure it out.

@BinaryBrain commented on GitHub (Nov 8, 2024): Hi Chris, For this job, I see the filename as: `originalFileName: 'example.pdf'`. Please make sure you're sending a filename with the correct extension when calling the API. If you send the snippet of your code, I can help you figure it out.
yindo commented 2026-02-16 00:17:27 -05:00
Author
Owner
Copy Link
Copy Source

@cmenge commented on GitHub (Nov 10, 2024):

Hi @BinaryBrain - thank you, that solves https://github.com/run-llama/llama_parse/issues/473, because passing the correct file extension indeed solves that problem.

As for this issue, I believe it should in any case pop up in the history with an error message that ideally explains this.

@cmenge commented on GitHub (Nov 10, 2024): Hi @BinaryBrain - thank you, that solves https://github.com/run-llama/llama_parse/issues/473, because passing the correct file extension indeed solves that problem. As for this issue, I believe it should in any case pop up in the history with an error message that ideally explains this.
yindo commented 2026-02-16 00:17:27 -05:00
Author
Owner
Copy Link
Copy Source

@BinaryBrain commented on GitHub (Jan 14, 2025):

We display failed job in the history now

@BinaryBrain commented on GitHub (Jan 14, 2025): We display failed job in the history now
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#316
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?