Summary
When configuring a decision table, setting the values field on the defaultsTo object for a queue column could cause the backend service to throw a Null Pointer exception, resulting in a 500 error response.
We’ve improved validation so that this invalid configuration is now treated as a client error. Instead of a 500 response, the API will return a 400 Bad Request with a descriptive error reason. This prevents unnecessary calls to downstream services (for example, for division checks) and makes it clearer to customers how to correct their request.
Effective Date
Monday, January 5, 2026
Details
Previously, an invalid defaultsTo configuration for a queue column could cause a Null Pointer exception in the backend service, which surfaced as a generic 500 error. We’ve fixed the backend to correctly classify this as a bad request and aligned the public API to return 400 in these cases.
Customer Impact
- Before: Invalid requests could result in a generic 500 error.
- After: The same invalid requests will now return 400 Bad Request with a reason, allowing customers to detect and correct configuration issues earlier.
- There is no impact for valid requests; only invalid defaultsTo configurations for queue columns are affected.
Impacted Resources
POST /api/v2/businessrules/decisiontables
PATCH /api/v2/businessrules/decisiontables/{tableId}
Issue References
[RULES-1050]
Contacts
@Brian Lennon Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.