With onError="stopOnError", QuickBooks answers every request after the first failure with 3231 instead of leaving it out
Observed 2026-10-06 on QuickBooks Enterprise Solutions 24.0 (US), reporting qbXML 17.0.
With onError="stopOnError", QuickBooks runs nothing after the first request that fails, but it does not leave the later requests out of its answer. Each one gets its own *Rs element with statusCode="3231", severity Error and the message "The request has not been processed."
This batch has a query that fails (bar codes are not enabled in the company file) followed by one that would succeed:
<?qbxml version="16.0"?>
<QBXML><QBXMLMsgsRq onError="stopOnError"><CompanyQueryRq requestID="1"/><BarCodeQueryRq requestID="2"/><HostQueryRq requestID="3"/></QBXMLMsgsRq></QBXML>
QuickBooks answered, with the CompanyRet cut short:
<CompanyQueryRs requestID="1" statusCode="0" statusSeverity="Info" statusMessage="Status OK"><CompanyRet>…</CompanyRet></CompanyQueryRs>
<BarCodeQueryRs requestID="2" statusCode="3250" statusSeverity="Error" statusMessage="This feature is not enabled or not available in this version of QuickBooks." />
<HostQueryRs requestID="3" statusCode="3231" statusSeverity="Error" statusMessage="The request has not been processed." />
The same three requests with onError="continueOnError" were answered 0, 3250 and 0, so the 3231 comes from the stop, not from HostQueryRq.
What to do
When you read a stopOnError batch, do not treat a 3231 after the first failure as a failure of that request. It means QuickBooks never ran it, so it is safe to send again once you have dealt with the request that failed. Match answers to requests by requestID rather than assuming the skipped ones are missing.
Not observed
- A failing add followed by a 3231; the failure here was a query.
- Whether writes made earlier in the batch are rolled back.
Error codes on this page
QuBe Sync is a JSON API for QuickBooks Desktop that is built on what these findings show.