Content: "Failed to Fetch Resource 400" Error Appears on Content Item Load

[zcolah]

Problem

When attempting to load a content item, the UI displays a "Failed to Fetch Resource 400" error. The user does not know what this means and if the content item has an issue in the first place that needs to be fixed.

Investigation Notes

@agalin920 was able to investigate and discover the error message is "Bad Request: invalid or unknown ZUID (859-441-7300) provided."

Upon further investigation, it was discovered that values in the format X-X-X (e.g., 859-441-7300) are mistakenly being treated as valid ZUIDs.

The frontend logic is attempting to fetch data for these values, leading to the 400 error.

Steps to Reproduce

1. Load a content item containing a single line text field with value in the format X-X-X (e.g. 859-441-7300).
2. Observe the "Failed to Fetch Resource 400" error on the UI.

Solutions

Field values in the X-X-X format should not be treated as ZUIDs and should not trigger data fetch requests. This will prevent the error from appearing in the UI as a notification as well.

Next Steps

• Investigate the frontend logic to determine why values in the X-X-X format are being treated as potential ZUIDs.
• Assess whether the logic for fetching data based on ZUIDs is still necessary for all field types.
• If the logic is required, ensure that only valid ZUIDs trigger fetch requests
• Potentially isolate fields that need ZUID lookup logic, particularly for internal link relationship fields