{"section":"known-issues","requestedLocale":"en","requestedSlug":"apps-using-masterdater-builder-2x-may-fail-to-identify-schemas-after-a-install","locale":"en","slug":"apps-using-masterdater-builder-2x-may-fail-to-identify-schemas-after-a-install","path":"docs/en/known-issues/Storage/apps-using-masterdater-builder-2x-may-fail-to-identify-schemas-after-a-install.md","branch":"main","content":"## Summary\n\n\nSome applications built using the Master Data build 2.x may experience runtime errors immediately after being installed in an account where they have not been previously installed (fresh installation). The automatic association between the installed app version and its data definition (schema) fails. As a result, the system cannot locate the necessary structure to save or read information, returning the error \"No associated schema was found\".\n\n\n#### Simulation\n\n\n\n- Install an app that uses the Master Data V2 builder and has never been installed in that environment before.\n- Open the application or trigger an action that requires reading or writing data to Master Data.\n- The operation will fail, and the error \"No associated schema was found\" may be observed in the logs or the interface.\n\n\n#### Workaround\n\n\nOpen a support ticket with the following information:\n\n\n- App name\n- Version\n- Entities used by the app"}