Resolved on May 8, 2026.
Earlier today, some print templates failed to convert to PDF. Retries usually worked. The print template system needs every asset (stylesheets, logos, barcodes) to load before it can produce a PDF. If one asset failed, the whole PDF failed. Two things were causing assets to fail: 1. our barcode service was returning errors on some request shapes after a library upgrade. 2. and some customer logos (and other assets) hosted on AWS were intermittently unavailable. We've fixed the barcode service. It now handles the request shapes the template renderer sends and retries once on a transient error. The AWS issue resolved on its own. Longer term, we want the renderer to keep going when an asset fails (e.g. fall back to a placeholder). We can't change the current renderer's behavior without risking layout shifts in your existing templates, so we're building a new version alongside it. The renderer will be versioned, and you'll be able to move templates over when you're ready. We're also adding monitoring on the barcode service and on template-render success rates so we catch this faster next time. Sorry for the disruption. If a print is still failing for you from this window, please retry. Contact support if it still doesn't work.
Update timeline
- resolved May 08, 2026, 02:51 PM UTC
Earlier today, some print templates failed to convert to PDF. Retries usually worked. The print template system needs every asset (stylesheets, logos, barcodes) to load before it can produce a PDF. If one asset failed, the whole PDF failed. Two things were causing assets to fail: 1. our barcode service was returning errors on some request shapes after a library upgrade. 2. and some customer logos (and other assets) hosted on AWS were intermittently unavailable. We've fixed the barcode service. It now handles the request shapes the template renderer sends and retries once on a transient error. The AWS issue resolved on its own. Longer term, we want the renderer to keep going when an asset fails (e.g. fall back to a placeholder). We can't change the current renderer's behavior without risking layout shifts in your existing templates, so we're building a new version alongside it. The renderer will be versioned, and you'll be able to move templates over when you're ready. We're also adding monitoring on the barcode service and on template-render success rates so we catch this faster next time. Sorry for the disruption. If a print is still failing for you from this window, please retry. Contact support if it still doesn't work.
Your product runs on more than Fulfil.IO
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services