We’ve identified an opportunity to improve the user experience around error handling in Harness form/API interactions.

Current Behavior:

When API calls fail (e.g., via form fields, button actions), the error response is displayed as raw JSON.

This exposes technical details directly to end users.

Impact:

Poor user experience, especially for non-technical users.

Makes it difficult for users to quickly understand what went wrong and how to take corrective action.

Inconsistent with standard UI/UX practices where errors are typically simplified and contextual.

Desired Behavior:

Provide clean, user-friendly error messages instead of raw JSON.

Ability to:

Map API error responses to readable messages

Customize or format error messages at the form level

Optionally hide technical details while preserving them for logs/debugging

Current Interim Approach:

We are continuing with raw JSON responses due to lack of alternative options.