Validate system configuration automatically and flag incompatible settings before they cause errors

Admins want the system to check for configuration issues proactively and surface clear warnings, so that incompatible settings are identified before they result in recurring upload errors or other failures. Problem / Pain: When a configuration change makes an existing setting incompatible with the rest of the system, the error only becomes visible at the point of use, for example, when a file is uploaded. The root cause can be very difficult to trace, as the connection between the configuration change and the resulting error is not obvious. Admins and configurators have to investigate manually, which is time-consuming and requires deep system knowledge. Impact / Benefit: A built-in configuration check that validates settings and flags incompatibilities proactively would allow admins to identify and resolve issues before they impact users. It would reduce investigation time, lower the risk of recurring errors going unnoticed, and make the system more resilient and transparent for organizations with complex or heavily customized configurations. Example use case: A configurator updates a field type in a customized system. The change makes the field incompatible with an existing folder-based tagging configuration. Instead of discovering this through a recurring upload error that is difficult to trace, a configuration check flags the incompatibility immediately after the change is made, pointing the configurator directly to the affected setting. Idea source: Internal suggestion Voting note: Vote for this idea if this need is relevant to you as well.