Jonas Bergqvist
Dec 8, 2016
  15129
(7 votes)

Exceptions in Find

Episerver Find can be used in many places on a site, like menus, navigations, listings, and searches. One thing that usually are forgotten when using Find is that it’s a service in the “cloud”, where you should handle possible exceptions.

EPiServer.Find.ServiceException

The “ServiceException” is the most important exception that should be handled in every place where Find is used. This exception will be thrown if the service is down, or if there is any other communication problem.

This exception inherits from ApplicationException.

EPiServer.Find.ClientException

The “ClientException” can be thrown when the query contains errors that is found at runtime. There is also several specific exceptions that inherit from “ClientException”.

This exception inherits from ApplicationException.

EPiServer.Find.SelfReferencingLoopException

The “SelfReferencingLoopException” will be thrown if a circular reference is found at runtime. There can for example exist a “Parent” property on a class, where the class of the parent property has a reference to the current class.

This exception inherits from ClientException.

EPiServer.Find.ProjectionException

The “ProjectionException” will be thrown if the projection (Select) is used in the wrong way in the query.

This exception inherits from ClientException.

EPiServer.Find.Api.InvalidIndexIdException

The “InvalidIndexIdException” will be thrown if the id of the index is null, or over 100 characters.

This exception inherits from ClientException.

EPiServer.Find.Api.InvalidDocumentIdException

The “InvalidDocumentIdException” will be thrown if the id of the document is null, or over 100 characters.

This exception inherits from ClientException.

EPiServer.Find.Api.InvalidSearchRequestException

The “InvalidSearchRequestException” will be thrown if the terms facet has been set to a value less than 0, or higher than 1000.

This exception inherits from ClientException.

Conclusion

Handle “EPiServer.Find.ServiceException” and “EPiServer.Find.ClientException” on all places where a query is created and executed against Find.

Dec 08, 2016

Comments

Please login to comment.
Latest blogs
Optimizely PaaS CMS Administrator Certification (2025): What to Expect and How to Prepare

The Optimizely PaaS CMS Administrator certification is best understood as training for the operational side of Optimizely CMS. It focuses on how th...

Augusto Davalos | Jun 2, 2026

Creating Read-Only Calculated Fields in Optimizely Commerce 14

Introduction In many Optimizely Commerce projects, product information comes from external systems such as ERPs, PIMs, inventory management systems...

Ankit Agarwal | Jun 2, 2026

Pushing Content Between Optimizely DXP Environments

We've been working with a client who has been on Optimizely 11 for a long time - self-hosted, on their own server infrastructure, with a content...

Matt Pallatt | Jun 2, 2026

Launching “Learning by Doing – Optimizely OPAL Series” | Episode 01 is Live!

  Introduction With Optimizely OPAL, we’re seeing a shift from "content management" to "intelligent content orchestration". But here’s the reality ...

Ratish | Jun 1, 2026 |