Skip to content

Catalog previews for heygen-avatar-promo-card and slack-notification-ad return HTTP 403 (missing CDN objects) #3283

Description

@AL-knows

Describe the bug

The two catalog blocks added in PR #3279 (heygen-avatar-promo-card, slack-notification-ad) reference preview media objects on the docs CDN that return HTTP 403. Both official catalog pages load, but their embedded preview videos fail to play (readyState=0, MEDIA_ERR_SRC_NOT_SUPPORTED) because the referenced .mp4/.png objects are not served.

Link to reproduction

The defect is in the hosted CDN objects, not the local toolchain, so the official pages themselves are the reproduction:

Steps to reproduce

  1. Open either catalog page above.
  2. The embedded preview video fails to load (readyState=0, MEDIA_ERR_SRC_NOT_SUPPORTED).
  3. GET the four preview objects directly — each returns HTTP 403.

Expected behavior

The four preview objects should be published at their source-declared URLs with the expected content types:

  1. https://static.heygen.ai/hyperframes-oss/docs/images/catalog/blocks/heygen-avatar-promo-card.mp4 — expect video/mp4
  2. https://static.heygen.ai/hyperframes-oss/docs/images/catalog/blocks/heygen-avatar-promo-card.png — expect image/png
  3. https://static.heygen.ai/hyperframes-oss/docs/images/catalog/blocks/slack-notification-ad.mp4 — expect video/mp4
  4. https://static.heygen.ai/hyperframes-oss/docs/images/catalog/blocks/slack-notification-ad.png — expect image/png

Actual behavior

All four return HTTP 403 (application/xml, Error from cloudfront).

For comparison, an established block's previews serve correctly:

  • https://static.heygen.ai/hyperframes-oss/docs/images/catalog/blocks/vfx-shatter.mp4 → HTTP 200 (video/mp4)
  • https://static.heygen.ai/hyperframes-oss/docs/images/catalog/blocks/vfx-shatter.png → HTTP 200 (image/png)

Likely cause

PR #3279 added the two blocks but the docs-image upload step was not run for them. Per the workflow in PR #301 (docs/images/static.heygen.ai CDN), after adding a catalog block a maintainer must run the catalog-preview generation and docs-image upload step (e.g. bun run generate:catalog-previews --only <name> then bun run upload:docs-images) to publish the preview objects; that step appears to have been skipped for these two blocks.

Request: please run the upload step for the two new blocks so the four objects above are served with the expected content types.

Environment

N/A — the defect is on the hosted CDN/docs side, not the local toolchain.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions