dashboard scheduled delivery failed: PDF rendering timeout error in Looker fix

TL;DR

Shrink what the renderer must produce first. Reduce the dashboard tile count or row limits, switch long tables to a paginated layout, and retry the PDF delivery before changing schedules. The renderer loads the whole dashboard in a headless browser under a stricter time budget than an interactive viewer gets, so a dashboard that merely feels slow on screen often times out as a PDF.

dashboard scheduled delivery failed: PDF rendering timeout error in Looker fix

Use this when

• Scheduled PDF deliveries fail or arrive intermittently while the dashboard opens in the browser.
• The dashboard has many tiles or very large table visuals.
• Delivery history shows the failure during rendering, before any send step.

Not for this skill when

• The delivery fails with a destination or format error. Fix the schedule settings instead.
• The dashboard itself times out interactively for every viewer. Fix the explore performance first.

Steps

1. Open the delivery history for the schedule and confirm the failure stage is rendering, and note the dashboard and format involved. Verify: the log shows a render timeout rather than a send or permission failure
2. Time an interactive load of the dashboard and identify the slowest tiles and any table visual returning thousands of rows. Verify: you can name the tiles that dominate the load time
3. Reduce table row limits, set sensible default filters for the delivery, and consider a delivery specific copy of the dashboard with fewer tiles. Verify: the trimmed dashboard loads noticeably faster in the browser
4. Send a one-off test delivery of the PDF to yourself from the schedule settings. Verify: the PDF arrives complete with all pages rendered
5. If the full dashboard must stay intact, split the schedule into two deliveries by section or move the heaviest tile to its own delivery. Verify: each split delivery succeeds in the delivery history
6. Restore the regular schedule and confirm the next automatic run succeeds end to end. Verify: the scheduled PDF is delivered at the expected time with current data

Why it happens

Rendering is a batch job with a hard window, not an interactive session a user can wait through. Dashboards grow tile by tile until the combined render crosses that window, which is why the failure often starts suddenly after a small addition. Keeping a delivery weight budget, and testing a PDF after adding tiles, prevents the schedule from becoming the place the problem is discovered.

Looker scheduled PDF delivery renders the dashboard server side, waiting for every tile query and visual to finish inside a fixed render window. Wide tables with thousands of rows, many tiles on one page, and a slow explore compound into a render that exceeds the window even though each tile eventually completes for a patient viewer. The delivery history shows the failure at the rendering stage rather than at query or destination stages.

Field notes for Looker specifically. The Admin area holds the diagnostic pages that matter here, System Activity for query history and runtimes, the PDT activity page for derived table builds, and the Content Validator under the content management tools. Keep the browser on the same Looker version as the instance when testing, because explore behaviour and error wording shift slightly between monthly releases. Screenshots from viewers are worth collecting with the exact load time, since Looker support and your own history search both work far better from a timestamp than from a description of slowness.

A practical habit for Looker teams is to keep one test user per permission tier and to test every model change as the most restricted tier, not as an admin. Admins bypass access filters, see every field, and hit warm caches, so admin testing systematically hides the failures viewers get. Pair that with a standing explore that lists the twenty slowest tiles across the instance each week, and most dashboard incidents become follow ups on a report the team already reads, instead of surprises reported by executives in a meeting.

Variants and edge cases

Looker PDF delivery rendering timeout scheduled dashboard

The scheduled-delivery phrasing matching the failure stage.

Looker schedule fails PDF too many tiles render

The tile-count variant for heavy dashboards.

Looker test delivery PDF timeout split dashboard fix

The split-delivery variant once trimming is not an option.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstJUaiTh9W4qlfZs8zGYa1A