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

Job Records from parsing/history missing Job Durations #424

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

Originally created by @adreichert on GitHub (Feb 7, 2025).

Describe the bug
About 75% of job records downloaded from the endpoint parsing/history are missing meaningful values in the field time. Instead there is a 0. I'd like to see if these times can be populated.

curl -L 'https://api.cloud.llamaindex.ai/api/v1/parsing/history' -H 'Accept: application/json' -H "Authorization: Bearer $LLAMA_CLOUD_API_KEY" | jq .

  {
    "user_id": [id]
    "day": "2025-02-07",
    "job_id": [id]
    "file_name": [file name]
    "original_file_name": [file name]
    "expired": false,
    "pages": 4,
    "images": 0,
    "time": 0. <--- Missing 
  },

 % curl -s -L 'https://api.cloud.llamaindex.ai/api/v1/parsing/history' -H 'Accept: application/json' -H "Authorization: Bearer $LLAMA_CLOUD_API_KEY" | jq 'map(select(.day >= "2025-02-05")) | {total: length, time_zero: map(select(.time == 0)) | length}'
{
  "total": 4191,
  "time_zero": 3250
}

Client:
Please remove untested options:

  • API

Additional context
Better job logging would help us better interact with LlamaParse

Originally created by @adreichert on GitHub (Feb 7, 2025). **Describe the bug** About 75% of job records downloaded from the endpoint `parsing/history` are missing meaningful values in the field `time`. Instead there is a `0`. I'd like to see if these times can be populated. ``` curl -L 'https://api.cloud.llamaindex.ai/api/v1/parsing/history' -H 'Accept: application/json' -H "Authorization: Bearer $LLAMA_CLOUD_API_KEY" | jq . { "user_id": [id] "day": "2025-02-07", "job_id": [id] "file_name": [file name] "original_file_name": [file name] "expired": false, "pages": 4, "images": 0, "time": 0. <--- Missing }, ``` ``` % curl -s -L 'https://api.cloud.llamaindex.ai/api/v1/parsing/history' -H 'Accept: application/json' -H "Authorization: Bearer $LLAMA_CLOUD_API_KEY" | jq 'map(select(.day >= "2025-02-05")) | {total: length, time_zero: map(select(.time == 0)) | length}' { "total": 4191, "time_zero": 3250 } ``` **Client:** Please remove untested options: - API **Additional context** Better job logging would help us better interact with LlamaParse
yindo added the bug label 2026-02-16 00:17:48 -05:00
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#424
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?