The carousel that rendered blank.

A renderer I run started shipping carousels where the first card's image was just... blank. Every other card was fine. Only the first.

Blank-on-the-first-one is a tell. It almost always means a race: something is being captured before it is ready.

What was happening

The pipeline builds each slide in a headless browser, then screenshots it. The images on the cards load from a remote CDN. The screenshot was firing the instant the page reported "done," but "page loaded" and "every image finished downloading" are not the same event. The first card lost the race most often because it had the furthest to travel.

The fix

The fix was one idea: do not screenshot until every image has actually finished. Wait for each one to reach a real loaded state, or to error, before capturing the frame. No model involved. No clever prompt. Just the oldest rule in automation, which is that you do not take the picture before the subject has arrived.

Do not take the picture before the subject has arrived.

The same bug, everywhere

Capture-before-load is the same bug as record-before-act and read-before-think. Different system, same lesson: finish step one before you start step two. Once you have seen it in one place you start catching it everywhere, including in AI workflows that report success a beat before the work is genuinely done.

If you build anything that screenshots or scrapes rendered pages, the interesting question is how you decide it is truly "ready." That definition is usually where the bug lives.