When caching contents of your application, you may force the cache to be invalidated, i.e., cached elements content it invalidated, forcing the evaluation on the next usage and, this way, have the cache updated with the most recent content.

Cache Invalidation

The elements of the cache can be invalidated in one of the following ways:

1. • In your eSpace: Service Studio provides you with two System Actions that invalidates the contents of the cache:

ESpaceInvalidateCache: all cached elements with binding to the eSpace are invalidated in all Front-end Servers. Learn more about this action;

TenantInvalidateCache: invalidates tenant specific caches across all Front-end servers. This action exists for compatibility purposes. Please use the EspaceInvalidateCache action to reduce the invalidation impact to a single eSpace. Learn more about this action.

Learn more about Using Cache in Multi-Tenant Applications.

1. • When a Front-end Server reboots: when the Platform Server starts, all elements in the cache are invalidated in all Front-end Servers.

   • When the eSpace is published: when the eSpace is published, all elements in the cache are invalidated in all Front-end Servers.

   • In Service Center: in the eSpace screen, you have the Redeploy Published Version button, which invalidates all elements in the cache in all Front-end Servers.

Automatic Element Invalidation

A cached element is invalidated when the elapsed time since the element content was last cached exceeds the element's  Cache in Minutes value.

See Also

About Caching Contents