Page Type, Component Type, and Custom Attribute Editor Caching

How long page types, component types, and custom attribute editors are cached in memory depends on whether the environment is sandbox, development, staging, or production. To refresh the page types, component types, and custom attribute editors on a production environment, or to refresh them immediately on other environments, a code version switch must occur. When you develop new page types, component types, or custom attribute editors, or modify existing ones, and then replicate them to a production environment, a best practice is to issue an event for a code version switch so that the page types, component types, and custom attribute editors are immediately refreshed.

Table 1. Cache Times for Page Types, Component Types, and Custom Attribute Editors
Environment Cache Refresh Interval
Sandbox 5 seconds or on code version switch
Development 5seconds or on code version switch
Staging 5 seconds or on code version switch
Production On code version switch