Result filters get executed in case of model-binding and/or model-validation failures.

[phougatv]

• Go to Filter types
• Under Result filters, the 2nd point: Run only when the action method executes successfully seems incorrect, because result-filters gets executed even in case of model-binding and/or model-validation failures. But action methods doesn't executes in case of model-binding and/or model-validation failures.
• Image for reference:
  

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: a70a955f-dd5a-c46b-dfe8-21521e619320
• Version Independent ID: ebb299e0-6c1c-7077-689d-ac711352e418
• Content: Filters in ASP.NET Core
• Content Source: aspnetcore/mvc/controllers/filters.md
• Product: aspnet-core
• Technology: aspnetcore-mvc
• GitHub Login: @Rick-Anderson
• Microsoft Alias: riande

[Rick-Anderson]

Can you provide a link to a public gitHub repo with the simplest possible sample that shows the problem?

[phougatv]

.NET version: 7.0.201
Here is the link. I have added a custom validation attribute by the name: GreaterThanZeroIntegerValidationAttribute. For this to fail try passing a value less than 1, and you will see, only result filters kick-in.

The following screenshot has 3 scenarios: The highlighted one (first & third) are fail cases where as the one not highlighted is successful one.

[phougatv]

Hey @Rick-Anderson! just wanted to know if this is a valid issue? Also, do let me know if I can provide any more info.

[serpent5]

In this context, I think "executes successfully" means that there are no exceptions. Model-binding failures, etc, aren't exceptions, and so the Result Filters run.