Which server-side processing configuration prevents data misalignment during asynchronous draw requests?

Synchronizing Asynchronous Data Updates

When implementing serverSide: true in DataTables (v2.x), the client relies on the draw parameter to ensure that the response from the server matches the specific request sequence initiated by the user. This is critical in environments where multiple AJAX requests for pagination or filtering may overlap due to network latency.

If the backend does not strictly track and return the draw counter provided in the request, the table may render stale data or display the wrong page of results after a rapid series of user interactions.

What is the expected behavior when the server returns a draw value that differs from the client's current counter? Does DataTables discard the response entirely, or does it attempt to render the data regardless of the sequence mismatch?