# Fail fast

## Feature

Throw **SearchParameterIsInvalidException** when developer use a field in wrong way

Using a collection with 2 fields with follow settings:

| Field  | Indexed | Stored |
| ------ | ------- | ------ |
| Field1 | False   | True   |
| Field2 | True    | False  |

Use cases:

| Use case     | Using method | Field1           | Field2           |
| ------------ | ------------ | ---------------- | ---------------- |
| Faceting     | FacetField   | Throws exception | Works well       |
| Faceting     | FacetQuery   | Throws exception | Works well       |
| Faceting     | FacetRange   | Throws exception | Works well       |
| Filtering    | Filter       | Throws exception | Works well       |
| Get contents | Fields       | Works well       | Throws exception |
| Search       | Query        | Throws exception | Works well       |
| Sorting      | Sort         | Throws exception | Works well       |

**NOTE**

See more in [**field options by use case**](http://wiki.apache.org/solr/FieldOptionsByUseCase);

## How to

**This feature is actived by default**

To active/inactive this feature, change your **SolrExpressOptions** and set **FailFast**, like below:

```csharp
    services
        .AddSolrExpress<TechProduct>(builder => builder
            .UseOptions(options =>
            {
                // ... Other settings
                options.FailFast = true
            })
            // ...  Other settings
            );
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://solr-express.gitbook.io/docs/5.0.1/tutorials/basic-features/fail-fast.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.