syntaqxA deploy no longer fails because Cloudflare's API stumbled once, and when one does fail it says why. Each of the last few deploys failed at one service's `wrangler deploy` (the runner, then agents and models), and the log showed only the trace of the request that failed, cut off before its reason. Now a `wrangler deploy` that fails for anything but a mistake in what is being deployed (a build that fails, a configuration that does not read) is tried again after 20 seconds and then a minute, which is harmless since deploying the same version again changes nothing, and each failure is reported by Wrangler's own error block, which carries the reason, rather than its last lines.14f96e9History
- ..
- 0001_init.sql
- 0002_projects.sql
- 0003_paused.sql
- 0004_redirects.sql
- 0005_domains.sql
- 0006_replaced_and_down.sql
- 0007_repo_deleted.sql
- 0008_detected.sql
- 0009_workspace_deleted.sql
- 0010_repo_deployments.sql
- 0011_workflow_builds.sql
- 0012_via_workflow.sql
- 0013_workflow_build_jobs.sql
- 0014_containers.sql
- 0015_telemetry.sql