Jonas Bergqvist
Dec 8, 2016
visibility 15392
star star star star star star
(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

error Please login to comment.
Latest blogs
Optimizely : Missing Language Manager Gadget Fix in CMS 12 After Upgrading to .NET 10

Recently, while upgrading an Optimizely CMS solution to .NET 10, we came across an issue where the Language Manager gadget completely disappeared...

Madhu | Aug 2, 2026 |

Flat or Nested? Weighing Your Content Modeling Options in Optimizely SaaS CMS

When building a headless site on Optimizely SaaS CMS, one of the earliest and most critical design milestones your team will face is defining your...

Vipin Banka | Jul 31, 2026

From SDK to Core: Modernizing Optimizely Configured Commerce for .NET 8 and .NET 10

The .NET Framework 4.8 clock is running out for Configured Commerce customizations. Handled well, this deadline is not a chore it is the cleanest...

Vaibhav | Jul 29, 2026

Parallel Development in Optimizely CMS SaaS: Shifting to a Schema Migration Mindset

  Part 3 of the Parallel Development series. The branch-scoped push script from Part 1 works. Run it on a feature branch where you've touched a...

Vipin Banka | Jul 25, 2026