When a batch request reaches a size or processing limit, the system cancels the transaction and returns unprocessed requests in the unserviced JSON array in the response.
While currently this is not pressing, the user can adjust to what is necessary based on the batch size, it might be a good feature to check default limits and have adjustable limits (or maybe they should be pulled from the instance).
Any returned/cancelled requests will need to be pushed back to be processed in another batch.
When a batch request reaches a size or processing limit, the system cancels the transaction and returns unprocessed requests in the unserviced JSON array in the response.
as per https://docs.servicenow.com/bundle/sandiego-application-development/page/integrate/inbound-rest/concept/batch-api.html
While currently this is not pressing, the user can adjust to what is necessary based on the batch size, it might be a good feature to check default limits and have adjustable limits (or maybe they should be pulled from the instance). Any returned/cancelled requests will need to be pushed back to be processed in another batch.