Design Publishing Queues That Survive Image Provider Outages

Описание и применение

Публикационные очереди, устойчивые к сбоям внешних поставщиков изображений, сохраняют статьи, отложив этап обработки медиа и ограничив повторные попытки, при этом фиксируя происхождение и проверяя конечный файл.

Задача

Publishing pipelines often reject articles when external image providers fail, causing loss of editorial content.

Результат

Articles no longer get dropped during temporary image provider outages; media stage retries are bounded, provenance is recorded, and deployment is verified, improving reliability.

Рабочий процесс

• Validate article editorially
• Check hero image availability
• If image fetch fails and error is transient, defer media stage with retryAfter 1h
• Persist article state as MEDIA_PENDING
• Retry provider queries within bounded limits (e.g., 2 retries, alternate search phrases)
• If a valid asset is found, bind provenance and transform image
• Verify transformed raster (dimensions, hash, MIME)
• Deploy asset and confirm public URL
• If deployment fails, keep article in pending state for retry

Доказательства

The retry design must respect Cloudflare Workflow limits and the provider's Pexels API documentation; provider failure does not decide whether the article itself is valid.

Источник

A temporary outage has changed editorial history. A better state model is: text VALIDATED MEDIA_PENDING MEDIA_SELECTED READY_TO_PUBLISH PUBLISHED

Источник

If an asset selection has already been recorded for article A revision 3, the retry should inspect that record before searching again.

Источник