Workers deployment compatibility_date transition: failed deploy triage when Workers Logs are empty

Bottom line

Empty Workers Logs after moving compatibility_date forward or adding nodejs_compat_v2 usually means the new Worker version was never activated. Workers Logs record requests served by an activated version, so a deploy that fails during validation or upload produces no version, no route assignment, and no log entries.

Signals that separate pre-activation from post-activation failure

Observation	Pre-activation failure	Post-activation failure
wrangler deploy result	Non-zero exit; validation or upload error naming compatibility_date, compatibility_flags, or a binding	Zero exit; deploy reports success
Dashboard versions	No new version; previous version still serves the route	New version listed and assigned to a route or preview
Workers Logs	Empty for the failing version because it never received requests	Errors or entries for the new version; empty logs can also mean no traffic, sampling, delay, or logging disabled

Confirm the nodejs_compat_v2 date requirement before deploying

1. Run wrangler --version; flag support and date requirements vary by Wrangler release.
2. Open the current Cloudflare Workers compatibility_flags reference matching that toolchain.
3. If nodejs_compat_v2 lists a minimum compatibility_date, set compatibility_date on or after it in wrangler.toml.
4. If no minimum is published, treat the requirement as undocumented and validate in staging before production.
5. Do not hardcode a date from older notes; it can change between releases.

Fields to diff between the last known-good and failing versions

Compare names, types, and presence only. Never compare or log secret values.

• compatibility_date
• compatibility_flags, especially nodejs_compat and nodejs_compat_v2
• main or module entry point
• Bindings for KV, D1, R2, Durable Objects, services, queues, Vectorize, and Analytics Engine
• vars and secret presence
• [env] overrides
• Routes, zone, and account

Triage steps

1. Re-run the failing deploy and capture the exit code and full error output.
2. If the command errors before creating a version, correct the configuration error and redeploy.
3. If the deploy succeeds, check the dashboard for a new version assigned to the route.
4. If a new version is active, send a test request to that route or preview and inspect Workers Logs and traces for that version. Errors there indicate a post-activation behavior change.
5. If logs remain empty after activation, verify that the route received traffic; absence of requests can also produce an empty stream.

Assumptions and uncertainty

This guidance assumes the Wrangler CLI and the Cloudflare Workers dashboard. Exact flag behavior and any minimum compatibility_date for nodejs_compat_v2 are version-sensitive and must be confirmed against current documentation for your wrangler --version. Empty logs alone are not proof of a pre-activation failure.

Missing diagnostic detail

Did wrangler deploy return an error, and does the dashboard show a new version assigned to the route? That answer determines whether to fix a pre-activation configuration error or investigate a post-activation runtime change.