$Batch Requests Logic

(5) Share

Report

Posted on by Jacob

192

Hi,

With $batch requests what is the logic for failures? From my testing, a batch request fails entirely upon encountering the first error. For example, if you have a batch request with 3 requests. Request 1 succeeds, request 2 fails then request 3 will not get processed.

From reading the MS documentation, it makes no mention of the first failure killing the entire batch only that in requests where Isolation: Snapshot header is present, it will rollback all successes upon the first error.

Is this standard behaviour or is there another header / field etc that can be added in order to 'bypass' this logic?

Thanks!

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (4)

Answers (1)

Suggested answer

Andrés Arias 5,166 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Hello,

I am not quite clear, in which process are you referring to? or which is the option to execute?

I hope I can help.

Regards,

Andres

Was this reply helpful? Yes No
Verified answer

Jacob 192 on at

Like (3)

Report
Copy link

Link copied!

@Andrés Arias thanks for the reply.

The problem was that the entire batch request would fail on the first request which returned an error rather than proceeding to the next request. If you had 5 requests within a batch:

- Req 1 = OK

- Req 2 = OK

- Req 3 = ERROR

then req 4 and 5 are dropped.

I did find this blog - Batch calls with Business Central (2) – Error handling – Kauffmann @ Dynamics 365 Business Central.

Adding the Prefer: odata.continue-on-error header solves this issue and gracefully handles the individual error of all requests within the $batch.

Hope this helps anyone else encountering this issue.

Was this reply helpful? Yes No
Suggested answer

Sohail Ahmed 11,169 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

By default, in Business Central $batch requests, if one operation fails, the entire batch stops processing — remaining requests are skipped.

To handle this gracefully and allow all requests to run even if some fail, add the header:

Prefer: odata.continue-on-error

This allows each request in the batch to be processed independently, and only the failed ones will return error responses.

✅ Mark this answer as verified if it helps you.

Was this reply helpful? Yes No
Gerardo Rentería Ga... 25,555 Most Valuable Professional on at

Like (2)

Report
Copy link

Link copied!

Hi, good day
I hope this can help you, and give you some hints.

Batch Requests in MS Dynamics 365 Business Central API.

Dynamics 365 Business Central: Batch API calls and max number of operations – Stefano Demiliani

Best Regards
Gerardo

Was this reply helpful? Yes No