How does exception filter precedence work when multiple filters are registered in NestJS?

Question

Accepted Answer

@UseFilters(HttpExceptionFilter)       // controller — handles any HttpException
@Controller('users')
export class UsersController {

@UseFilters(NotFoundExceptionFilter)   // method — handles NotFoundException first
  @Get(':id')
  findOne() {}

@Get()
  findAll() {} // only HttpExceptionFilter applies here
}

// Exception thrown → filter resolution order:
// NotFoundException on findOne():
//   1. NotFoundExceptionFilter (method) — matches, handles it
// UnauthorizedException on findOne():
//   1. NotFoundExceptionFilter (method) — does not match
//   2. HttpExceptionFilter (controller) — matches, handles it
// TypeError on findAll():
//   1. HttpExceptionFilter (controller) — does not match HttpException
//   2. AllExceptionsFilter (global) — matches, handles it Method-level filters are checked first, then controller-level, then global. The first filter whose @Catch() type matches the thrown exception handles it. @Catch(NotFoundException) will NOT handle BadRequestException — the types must match. @Catch() with no argument matches everything — use only at the global level. Multiple @Catch() types are supported: @Catch(NotFoundException, BadRequestException).

How does exception filter precedence work when multiple filters are registered in NestJS?

Scenario Questions

Follow-up Questions