syntaqxA workspace runs up to 12 jobs at once on g1t's machines while the pool has room, not 4. Every workspace was held to 4 hosted jobs at once (RUNNING_PER_WORKSPACE), so flagon-io's own CI and Deploy, about 13 jobs between them, waited their turn: 108 to 518 seconds after their runs were made, for 29aba25d, 58def404 and 0a5d1f6d, though the pool of 40 sandboxes (20 standard, 10 g1t-2core, 10 g1t-4core) was mostly idle. A workspace still always has its 4; past them, start_queued starts more, up to 12 (BURST_PER_WORKSPACE), while every workspace's hosted jobs together leave 8 sandboxes free (POOL_HEADROOM), so another workspace's first jobs still start at once (has_room). Deploy's own concurrency group still lands one deploy at a time. The architecture's Compute limits say so. Checked: cargo test -p g1t-actions-service (115 passing), npm run test:deploy (92).36c7309History
- ..
- about.rs
- activity.rs
- addresses.rs
- alerts.rs
- archives.rs
- audit.rs
- billing.rs
- blobs.rs
- broker.rs
- caches.rs
- checks.rs
- commits.rs
- contents.rs
- coordination.rs
- deploy_keys.rs
- deployments.rs
- folios.rs
- follow.rs
- lib.rs
- limits.rs
- logs.rs
- mcp.rs
- notifications.rs
- oauth.rs
- oidc.rs
- onboarding.rs
- openapi.rs
- operations.rs
- packages.rs
- people.rs
- pins.rs
- projects.rs
- protection.rs
- reference.json
- renamed.rs
- responses.rs
- rest.rs
- rules.rs
- run_artifacts.rs
- runners.rs
- security.rs
- telemetry.rs
- token_policy.rs
- toolkit.rs
- tools.rs
- why.rs