Existing documentation URL(s)

• https://developers.cloudflare.com/workers/observability/profiling-in-production/
• https://developers.cloudflare.com/workers/previews/test-and-debug/

What changes are you suggesting?

Please document whether deployed native Worker Previews can use CPU profiling, and how to target one specific Preview deployment if supported.

The profiling documentation uses:

POST /accounts/{account_id}/workers/workers/{worker_id}/versions/{version_id}/profile

Native Previews expose their deployments through:

GET /accounts/{account_id}/workers/workers/{worker_id}/previews/{preview_id}/deployments/{deployment_id}

The native Preview deployment response has a deployment id and number, but no documented version_id mapping. This leaves it unclear which identifier the profiling endpoint should accept for an existing native Preview deployment.

Please clarify:

1. Is CPU profiling supported for native Preview deployments?
2. If supported, what official API or CLI path and identifiers target a specific current Preview deployment? Is there a deployment-to-version mapping?
3. Does the dashboard support selecting that exact native Preview deployment and downloading raw pprof data? If so, please document the selection and export steps.

If this environment is unsupported, please state that limitation on the profiling and Preview debugging pages.

This matters when investigating the exact deployed Preview code without creating another deployment, changing production, or using an unverified latest target.

Additional information

Read-only preflight observed on 2026-10-14:

• The native Preview deployment GET returned HTTP 200; the deployment was current, and its commit annotation matched the intended code.
• GET /accounts/{account_id}/workers/workers/{worker_id}/versions/{native_preview_deployment_id} returned Cloudflare error 10071: “The requested Worker version could not be found, please check the ID being passed and try again.”
• GET /accounts/{account_id}/workers/workers/{worker_id}/versions returned HTTP 200 with an empty result array.
• No profiling POST was issued because a valid target version could not be established.

The 10071 error above came from the version lookup GET, not from the profiling endpoint. Account profiling entitlement and runtime profiling availability have not been inferred from that error.

Identifiers are placeholders; account details, credentials, private repository names, Preview URLs, commit SHAs, and deployment IDs are omitted.