{"section":"known-issues","requestedLocale":"en","requestedSlug":"size-of-content-files-can-cause-problems-in-site-editor-features","locale":"en","slug":"size-of-content-files-can-cause-problems-in-site-editor-features","path":"docs/en/known-issues/CMS/size-of-content-files-can-cause-problems-in-site-editor-features.md","branch":"main","content":"## Summary\n\n\nEvery content or structure update in a store theme is registered in files called `content.json` and `template.json`, those files work like \"maps\" that keep the references of all the content that the storefront shows, therefore, it is also based on what is displayed as a preview in the Site Editor.\n\nWhen one of those files is too big, it can cause performance problems and affect Site Editor features like Content Version Scheduling.\n\n\n##\n\n## Simulation\n\n\nThere's no specific way to simulate problems based on content files size, but here's an example of a scheduled content fail:\n\nWhen a content file is too big the GET request, which is responsible to update the info on the screen, can present a timeout error, so, the content used could be based on the render-server cache, which will contain outdated information regarding the changes made in the new content version, causing the schedule fails.\n\n\n##\n\n## Workaround\n\n\n- It's essential to understand why those files are big and try to decrease them;\n- Check if the store has multiple bindings and if they are well set and indispensable because they can directly affect the size of the content files;\n- Check if the `vtex.render-server` and the `vtex.store` app are in their final version;\n- In a scheduled fail scenario, the user can manually activate the failed version."}