Best Practices for Extracting Metadata from Non-200 HTTP Response Bodies in Action Chains

Summary:

I am integrating a REST API in Oracle Visual Builder that returns distinct JSON schemas for success (HTTP 200) and failure (HTTP 400). My Service Connection is currently configured only with the success sample schema.

When the API returns a 400 error, the response body contains a specific error object (e.g., errorCode, message, details). However, because the Service Connection is bound to the success schema, I am struggling to programmatically access these error-specific fields within my Action Chain's failure path.

Is there a standard pattern in VBCS to parse and map "Bad Request" payloads that do not conform to the primary success schema without manually defining every possible error structure in the Service Connection?