What belongs in an Angular ErrorHandler, and what should be handled closer to the failure?

Handles expected failures at their callsite and reserves ErrorHandler for reporting unexpected framework or global failures with useful context.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I handle expected API, validation, and workflow failures where the operation is started so the UI can recover with the right context. Angular's ErrorHandler is for unexpected errors the framework forwards, and a custom handler can report them to observability infrastructure. It should not turn every failure into the same toast or pretend the application recovered when its state may be invalid.

Full answer below

Practice focus

Angular ErrorHandler, global error listeners, RxJS errors, recovery, observability, privacy, and error boundaries.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
The code that initiated an expected operation usually has the context to recover; a global handler usually does not.
I handle expected API, validation, and workflow failures where the operation is started so the UI can recover with the right context. Angular's ErrorHandler is for unexpected errors the framework forwards, and a custom handler can report them to observability infrastructure. It should not turn every failure into the same toast or pretend the application recovered when its state may be invalid.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
The report includes release, route template, browser context, feature, and a normalized stack while excluding tokens, request bodies, and user-entered data. Browser error and listeners cover failures outside Angular's normal call path when configured. RxJS streams use local only where there is a meaningful fallback; otherwise the error remains visible. A fatal screen can offer reload or safe navigation while a local panel failure remains local.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Using ErrorHandler as the normal API error path.
Sending full application state and user input with every exception.
Catching errors and returning an empty value without a defined fallback.

What belongs in an Angular ErrorHandler, and what should be handled closer to the failure?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Next interviewer turn

Tech stacks

Skill areas

Was this drill useful?

Found this answer useful?

Human editorial direction

What belongs in an Angular ErrorHandler, and what should be handled closer to the failure?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Next interviewer turn

Tech stacks

Skill areas

Start a conversation

Was this drill useful?

Found this answer useful?

Human editorial direction