Cloudflare Workers dashboard shows “Unknown” as the source of cf CLI deployments

Aperta
  • Qualcosa non va?
#475 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
30/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
cloud, devtools

Direzione di ricerca

The report is about the dashboard's Source column showing Unknown for deployments whose API metadata reports cf_cli, so the cause may lie outside this repository. Start in packages/cli/src/version.ts, where USER_AGENT is defined, and in packages/cli/src/lib/deploy-context.ts, where it reaches the deployment request. Done means confirming which metadata field the dashboard reads and whether the CLI sends it; the issue itself says the dashboard mapping is not established.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

upstream
Summary of the issue

After a successful cf deploy --prebuilt --mode production with [email protected], the Workers dashboard's Deployments → Deployment activity → Source column displays Unknown.

Affected page: Cloudflare dashboard → select an account → Workers & Pages → select a Worker → Production → Deployments. Within Deployment activity, the Source column displays Unknown.

Page URL pattern (account and Worker identifiers replaced with placeholders):

https://dash.cloudflare.com/<account-id>/workers/services/view/<worker-name>/production/deployments
Cloudflare Workers Deployments page in light mode showing Ready deployments with source Unknown

Screenshot captured in Cloudflare dashboard Light mode during a follow-up check on 2026-11-02. Cropped to exclude the account URL, Worker name and version IDs; the Deployments navigation and the Ready / Unknown values are unchanged.

For the same version, both the newer Workers API (read through cf workers versions get) and the script-versions REST API report cf_cli. The deployment record also reports cf_cli.

Rechecked on 2026-11-02 at approximately 05:01 UTC, about 15 minutes after deployment, in a newly opened dashboard tab. The version ID shown in the dashboard matches the API responses. The same symptom occurred with 1.0.0-beta.24 before upgrading and redeploying.

Deployment succeeds, the new version serves 100% of traffic, and the application responds over HTTPS. This report concerns the displayed deployment source: it makes a deployment from the official CLI look unrecognized.

Expected behaviour

Display a recognizable label such as Cloudflare CLI for a version whose source is cf_cli.

If additional metadata is required, please document it or have cf deploy supply it. I could not find a source-label option in the deploy command. Please route this to the dashboard/API owners if that is where the discrepancy belongs; I have not established which internal component causes it.

Version of cf used

1.0.0-beta.26 (also observed with 1.0.0-beta.24).

System information and package versions
  • macOS 27.2, arm64
  • Node.js 26.12.1
  • @cloudflare/vite-plugin: 2.0.0-beta.v.8
  • Vite: 7.3.7
  • Project configuration: cloudflare.config.ts
  • Authentication: API token
  • Deployment path: prebuilt output published by the locally installed cf binary
Reproduction (optional)

These are the steps used with an existing application; I have not reduced it to a minimal public repository or tested the non-prebuilt path.

  1. Build and publish the configured Worker: 
    cf build --mode production
cf deploy --prebuilt --mode production
  2. Read the active deployment and its version: 
    cf workers deployments list --worker <worker-name> --mode production
cf workers versions get <version-id> --worker-id <worker-name> --mode production
  3. Cross-check that same version with: 
    GET /accounts/{account_id}/workers/scripts/{script_name}/versions/{version_id}
  4. Open the Cloudflare dashboard page using the navigation path above and compare the matching version’s Source column in Deployment activity.
Relevant error logs (optional)

No deployment error. Selected response fields only; identifiers, bindings and author information are omitted:

Surface Observed value
cf workers deployments list: matching deployment's source cf_cli
cf workers versions get: matching version's source cf_cli
Script-versions REST API: result.metadata.source cf_cli (HTTP 200, success: true)
Dashboard: same version's Source Unknown
Dashboard: Status / Triggered by Ready / by API token

The script-versions API reference explicitly lists cf_cli as a supported source, distinct from unknown.

The beta.26 source defines USER_AGENT = cf-cli/${VERSION} and passes it through the deployment request context. This supports checking the CLI/dashboard integration, but does not establish a specific dashboard mapping or caching bug.

Lingua principale
TypeScript
Stelle
993
Fork
65
Merge medio
18h 28m
PR unite (30g)
207

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cloudflare/cf

Tutte le issue di cloudflare/cf

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.