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
- ..
- 0001_init.sql
- 0002_lifecycle.sql
- 0003_repo_settings.sql
- 0004_up_to_date.sql
- 0005_assignees.sql
- 0006_merge_rules.sql
- 0007_timeline.sql
- 0008_plans.sql
- 0009_lifecycle_snapshot.sql
- 0010_merge_queue.sql
- 0011_agent_messages.sql
- 0012_exchanges.sql
- 0013_commit_statuses.sql
- 0014_mergeability.sql
- 0015_agent_runs_and_memory.sql
- 0016_by_author.sql
- 0017_agent_mentions.sql
- 0018_guardrails.sql
- 0019_memory_capture.sql
- 0020_agent_waits.sql
- 0021_confidence.sql
- 0022_required_checks.sql
- 0023_read_paths.sql
- 0024_g1t_name.sql
- 0025_requested_by.sql
- 0026_code_owners.sql
- 0027_labels_milestones_bases.sql
- 0028_rulesets.sql
- 0029_commit_checks.sql
- 0030_comment_edits.sql
- 0031_mention_revisions.sql
- 0032_contributions.sql
- 0033_agent_comments.sql