run-llama/llama_cloud_services
1
0
Fork 0
mirror of https://github.com/run-llama/llama_cloud_services.git synced 2026-08-26 16:56:36 -04:00
Code Issues 352 Packages Projects Releases 10 Wiki Activity

Issue with sending the Webhook #265

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

Originally created by @wus-solutions on GitHub (Sep 11, 2024).

Originally assigned to: @BinaryBrain on GitHub.

If I parse a document in the sandbox and specify a webhook, the document is parsed, but the webhook is not executed. No credits are calculated either, although the Markdown is displayed in full in the sandbox (JobId: 5a04a678-630d-47ad-84f8-3a373fd830c0). If I use the same document in the sandbox but without the webhook, I am charged the credits (JobId: 5371c0d1-63c3-4d58-8e31-62fa8306169f). There seems to be a problem with this PDF, as my normal workflow via API works with other PDFs. Unfortunately I can't see what the problem is.

Originally created by @wus-solutions on GitHub (Sep 11, 2024). Originally assigned to: @BinaryBrain on GitHub. If I parse a document in the sandbox and specify a webhook, the document is parsed, but the webhook is not executed. No credits are calculated either, although the Markdown is displayed in full in the sandbox (JobId: 5a04a678-630d-47ad-84f8-3a373fd830c0). If I use the same document in the sandbox but without the webhook, I am charged the credits (JobId: 5371c0d1-63c3-4d58-8e31-62fa8306169f). There seems to be a problem with this PDF, as my normal workflow via API works with other PDFs. Unfortunately I can't see what the problem is.
yindo added the bug label 2026-02-16 00:17:19 -05:00
yindo closed this issue 2026-02-16 00:17:19 -05:00
yindo commented 2026-02-16 00:17:19 -05:00
Author
Owner
Copy Link
Copy Source

@BinaryBrain commented on GitHub (Sep 11, 2024):

Hi @wus-solutions,
On your first job (5a04a678-630d-47ad-84f8-3a373fd830c0) you had a "Cache Hit", in which case we simply return the cached result (free of charge) and the webhook isn't called.
That said, we can consider the webhook not being called as a bug and we'll add it on the cached results as well.

@BinaryBrain commented on GitHub (Sep 11, 2024): Hi @wus-solutions, On your first job (5a04a678-630d-47ad-84f8-3a373fd830c0) you had a "Cache Hit", in which case we simply return the cached result (free of charge) and the webhook isn't called. That said, we can consider the webhook not being called as a bug and we'll add it on the cached results as well.
yindo commented 2026-02-16 00:17:19 -05:00
Author
Owner
Copy Link
Copy Source

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

This now should work as expected in production. thanks for reporting the bug.

@hexapode commented on GitHub (Sep 12, 2024): This now should work as expected in production. thanks for reporting the bug.
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#265
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?