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
- ..
- invites
- access.rs
- account_deletion.rs
- admin.rs
- aliases.rs
- avatars.rs
- crypto.rs
- deletion.rs
- deploy_keys.rs
- device.rs
- directory.rs
- dock.rs
- email.rs
- emails.rs
- github.rs
- invites.rs
- job_tokens.rs
- lib.rs
- members.rs
- oauth.rs
- paid.rs
- people.rs
- profiles.rs
- rename.rs
- run_credentials.rs
- security.rs
- shared_invites.rs
- sounds.rs
- teams.rs
- throttle.rs
- token_reach.rs
- tokens.rs
- two_factor.rs
- workspaces.rs