Skip to main content

Error handling

MarkpdfService propagates errors like standard Angular HttpErrorResponse, unless you log markpdfErrorInterceptor (see Framework Guide), in which case it normalizes them to MarkpdfClientError.

Without interceptor: HttpErrorResponse

With markpdfErrorInterceptor: MarkpdfClientError

kind table

"forbidden" covers both 401 and 403 because, from the point of view of the end user of your Angular app, they both mean the same thing: your backend could not authenticate against API. User can’t fix it — it’s a configuration issue on your end.

Reintentos

@markpdf/angular does not automatically retry on its own — delegate that responsibility to the SDK you use in your backend (Node.js, Python, C++…), which does have configurable retries. See Node.js SDK Error Handling for the recommended server-side pattern. If you need to retry from Angular itself (for example, a 429 call to your backend), use the standard RxJS operators: