It's a registry data gap, not a UI bug. The webapp shows the placeholder because the cloud connector registry has iconUrl: null for those connectors even though every one of them has an icon.svg in the repo and the icon is already sitting on the CDN (e.g. connectors.airbyte.com/files/metadata/airbyte/destination-aws-datalake/latest/icon.svg returns 200).
Scope: 18 of 44 cloud destinations and 38 of 583 sources are missing iconUrl.
Pattern: every affected connector was last published before the registry pipeline migration on 2026-03-20. Their per-connector registry entries (latest/cloud.json) were bulk-written at 00:09 UTC that day with iconUrl: null; the icon files were copied over ~4 hours later. Connectors published since then get a deterministic CDN icon URL from the new generator, so they're fine. Nothing has re-generated the stale entries because these connectors haven't shipped a release since. (That's why it skews "marketplace" — community connectors release rarely.)
Fix options:
- Re-generate/republish registry entries for the 56 affected connectors (a metadata-only publish is enough; no version bump needed).
- Make the registry compile step fill iconUrl deterministically when the icon exists on the CDN, so legacy entries self-heal.
- Webapp fallback to the CDN path when iconUrl is null (belt-and-suspenders).
It's a registry data gap, not a UI bug. The webapp shows the placeholder because the cloud connector registry has iconUrl: null for those connectors even though every one of them has an icon.svg in the repo and the icon is already sitting on the CDN (e.g. connectors.airbyte.com/files/metadata/airbyte/destination-aws-datalake/latest/icon.svg returns 200).
Scope: 18 of 44 cloud destinations and 38 of 583 sources are missing iconUrl.
Pattern: every affected connector was last published before the registry pipeline migration on 2026-03-20. Their per-connector registry entries (latest/cloud.json) were bulk-written at 00:09 UTC that day with iconUrl: null; the icon files were copied over ~4 hours later. Connectors published since then get a deterministic CDN icon URL from the new generator, so they're fine. Nothing has re-generated the stale entries because these connectors haven't shipped a release since. (That's why it skews "marketplace" — community connectors release rarely.)
Fix options: