From 7d62554989c5f12b49fffccbda5000272027d6c2 Mon Sep 17 00:00:00 2001 From: Malte Rohde Date: Mon, 19 Jan 2026 09:00:17 +0100 Subject: [PATCH] Rephrase timeout exception To make it clear that this is by no means a ChromicPDF bug, but usually a result of some user template taking too long to render. Relates to #343 --- lib/chromic_pdf/pdf/browser/channel.ex | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/lib/chromic_pdf/pdf/browser/channel.ex b/lib/chromic_pdf/pdf/browser/channel.ex index f3772d6..2b6d6d8 100644 --- a/lib/chromic_pdf/pdf/browser/channel.ex +++ b/lib/chromic_pdf/pdf/browser/channel.ex @@ -28,12 +28,12 @@ defmodule ChromicPDF.Browser.Channel do not able to complete the current operation (= PDF print job) within the configured #{timeout} milliseconds. + Out of the many reasons for why this may happen, most commonly the browser failed to emit + the `frame_stopped_loading` event on time. Please see the process state printed below. + If you are printing large PDFs and expect long processing times, please consult the documentation for the `timeout` option of the session pool. - If you are *not* printing large PDFs but your print jobs still time out, this is likely a - bug in ChromicPDF. Please open an issue on the issue tracker. - --- Current protocol: