qbXML status code 3231
ErrorQuickBooks didn't run this request: an earlier request in the batch failed under stopOnError, or, for a request sent alone, the company file doesn't allow it.
What QuickBooks says
The request has not been processed.
It arrives on the response element as statusCode="3231" statusSeverity="Error", with this text in statusMessage.
What to do
In a batch, fix the first failed request and send the rest again. Sent alone, it usually means the company file's edition, preferences or subscriptions don't include the feature.
Seen from a real company file
-
Answering LeadQuery:
The request has not been processed.
Things to know
- With onError="stopOnError", QuickBooks answers every request after the first failure with 3231 instead of leaving it out
- QuickBooks declines requests its edition, preferences or subscriptions don't allow, sometimes with 3231 "not processed" for a request sent alone
With QuBe Sync's API
QuBe Sync reads QuickBooks' response for you. When LeadQuery gets this code, your webhook receives this JSON:
{
"error": {
"debug_message": null,
"error_code": 3231,
"error_type": "quickbooks_business_error",
"hresult": null,
"message": "The request has not been processed.",
"user_message": "QuickBooks didn't run this request. Either an earlier change in the same batch failed, or this company file doesn't include the feature it needs."
},
"state": "error"
}
Wording read from QuickBooks Enterprise Solutions 24.0 (R21_80).