syntaqxA job that runs again is no longer stopped by the time cap of the attempt before it. A sandbox's Durable Object is named for its work (actions:{job} for a workflow job), and a re-run keeps the job's id, so every attempt of a job runs in the same object; each attempt scheduled its time cap's alarm there and none cleared it. The Desktop release's Linux job showed it: attempt 1 started at 12:47:17 with a 60-minute cap, so its alarm fired at 13:50:17, four minutes into attempt 3, and stopped attempt 3's build mid-compile (its log's last line is at 13:50:17). Now a sandbox clears the alarm, the cap and the stop reason an earlier attempt left when it starts, and the alarm stops a run only once that run has used its own whole cap, so alarms already scheduled before this deploy cannot do it either.89d501cHistory
- ..
- 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