Skip to main content

Not all responses are being sent to the webhook

Bug Report

Good morning,

We have a flow in Power Automate from which we send the documents to be processed. Then we have another flow with a webhook where the document is sent. The issue is that since last night, we are not receiving all the responses to the webhook. Out of 23 documents sent last night, we only received the response for 2.

I thought it might be due to too many API calls per second (although I haven’t received any errors, and in subsequent submissions I do receive a 202 response for all documents), so I added a 15-second delay between each call. In the first batch sent a little while ago, we received responses for 4 documents, in the next batch 4 more, then 6, and in the last one 7.

I also want to point out that in the web panel the number of processed pages is increasing, so the documents seem to be processed, but the webhook responses are not always being received.

This has never happened to us before. Could you please let me know if there is any kind of issue or limitation with the webhooks on your side?

Thank you,
Best regards

Posted by Sergio Rigo ·
Status: Completed8 comments

Log in to comment and vote

Comments8

  • Sergio Rigo

    •

    Sep 16, 2025

    Hello again,

    Unless I missed them, it has happened again with some documents. I’m sharing the IDs and timestamp of two of them.

    I am still keeping the RAG deactivated in all the calls.

    “id”:"4d1f677b-bf1b-4032-85db-3b6e86d131b6"

    "Date": "Tue, 16 Sep 2025 02:00:39 GMT”

    "id": "203d84a4-1aa1-4dbb-91ba-01e713720157"

    "Date": "Tue, 16 Sep 2025 02:01:13 GMT"


    Best regards

    • Ianaré Sévi

      Team•

      Sep 16, 2025

      Hi Sergio,

      Thanks for the detailed report.

      We published an improvement recently, can you test again on the same documents?

      (it might not still work on 100% of documents, improvements are ongoing)

      Thank you for your understanding

      • Sergio Rigo

        •

        Oct 3, 2025

        Oh, sorry, I didn’t see this! I can’t test now with that documents, but if it happens again I say you. I understand it’s still not recommended to activate the RAG.

        • Ianaré Sévi

          Team•

          Oct 3, 2025

          There’s been several improvements to RAG published over the past couple weeks. We have several high-volume users with RAG activated and not having this problem. I would say to test on documents that failed in the past and if everything is OK to activate RAG again.

  • Sergio Rigo

    •

    Sep 3, 2025

    Hello, we are using V2. The webhook id exist in the interface.

    This is one of them:

    "id": "4de21ff3-6f02-4c18-bc3d-4b1cc7f106d8"

    “Date": "Wed, 03 Sep 2025 00:02:45 GMT

    Then in another call has been processed with this id and time:

    "id": "0a590465-0ddd-4ffe-979c-e3f21d8da13d"

    "Date": "Wed, 03 Sep 2025 08:10:32 GMT"


    I can send you the full response, as well as the document and the images by email. I don’t want to upload anything here publicly because they are invoices and sensitive documents.

    Thank you for your quick response


  • Sebastian Olivera Silvera

    •

    Sep 3, 2025

    Hello,

    Thank you for submitting this ticket. Our team is looking into the issue.
    In the meantime, could you provide us with the following information:

    • Are you using the V1 of the Mindee API, or the V2?

      • If you are using the V2, do the webhook_ids you provided still exist in the interface?

    • Did you store any of the IDs of the jobs? Barring that, did you store their timestamp?

    • Would you mind sending a screenshot of the processed images on the interface?

    Thanks in advance