fix: add last active column to step concurrency table

[mnafees]

Description

This PR adds a new last_active column to v1_step_concurrency to mirror v1_queue

Type of change

• New feature (non-breaking change which adds functionality)

Checklist

Changes have been:

• Tested (unit, integration, or manually with steps specified)
• Linted and formatted
• Documented (where applicable)

---

🤖 AI Disclosure

• I acknowledge that an LLM was used in the creation of this Pull Request, in accordance with Hatchet's AI_POLICY.md.

• Details: [e.g. generating tests, writing docs]

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hatchet-docs	Ready	Preview, Comment	Jun 29, 2026 9:14am

[github-actions]

Benchmark results

goos: linux
goarch: amd64
pkg: github.com/hatchet-dev/hatchet/pkg/scheduling/v1
cpu: AMD Ryzen 9 7950X3D 16-Core Processor          
              │ /tmp/old.txt │         /tmp/new.txt          │
              │    sec/op    │    sec/op     vs base         │
RateLimiter-8   49.14µ ± 15%   49.35µ ± 38%  ~ (p=0.589 n=6)

              │ /tmp/old.txt │         /tmp/new.txt          │
              │     B/op     │     B/op      vs base         │
RateLimiter-8   137.7Ki ± 0%   137.7Ki ± 0%  ~ (p=0.660 n=6)

              │ /tmp/old.txt │          /tmp/new.txt          │
              │  allocs/op   │  allocs/op   vs base           │
RateLimiter-8    1.022k ± 0%   1.022k ± 0%  ~ (p=1.000 n=6) ¹
¹ all samples are equal

_{Compared against main (f34b10a)}

[mnafees]

We also want to update the v1_step_concurrency when the last_active has been stale for more than an hour - hence a very hot strat will only update the last_active every hour rather than every time.

[Copilot]

Pull request overview

This PR introduces a last_active_at timestamp on v1_step_concurrency to better track recent strategy activity (mirroring v1_queue) and uses it to gate stale strategy deactivation, reducing unnecessary cold-start churn.

Changes:

• Add last_active_at to v1_step_concurrency (schema + migration) and include it in sqlc-generated models/queries.
• Update the concurrency-slot insert trigger to refresh last_active_at when strategies are reactivated / periodically (throttled) on activity.
• Re-enable the periodic “deactivate stale step concurrency” controller operation and update the deactivation query to only deactivate strategies inactive for >1 day.

Reviewed changes

Copilot reviewed 3 out of 6 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
sql/schema/v1-core.sql	Adds last_active_at to v1_step_concurrency and refreshes it in the slot-insert trigger logic.
cmd/hatchet-migrate/migrate/migrations/20260629110253_v1_0_120.sql	Migration to add last_active_at and update the trigger function for existing installs.
pkg/repository/sqlcv1/models.go	Extends V1StepConcurrency with LastActiveAt.
pkg/repository/sqlcv1/workflows.sql.go	Updates RETURNING columns to include last_active_at for step concurrency creation flows.
pkg/repository/sqlcv1/concurrency.sql	Adds last_active_at gating to stale deactivation query.
pkg/repository/sqlcv1/concurrency.sql.go	Regenerated sqlc output reflecting the updated stale deactivation and selects.
internal/services/controllers/task/controller.go	Re-enables the periodic stale step-concurrency deactivation operation pool.
internal/services/controllers/task/deactivate_stale_step_concurrency.go	Implements the operation method that invokes the repository deactivation query.
pkg/scheduling/v1/tenant_manager.go	Threads ctx into concurrency-strategy updates (currently unused in the methods).
pkg/scheduling/v1/concurrency.go	Minor formatting-only change.

Files not reviewed (3)

• pkg/repository/sqlcv1/concurrency.sql.go: Generated file
• pkg/repository/sqlcv1/models.go: Generated file
• pkg/repository/sqlcv1/workflows.sql.go: Generated file

Comments suppressed due to low confidence (1)

sql/schema/v1-core.sql:913

• The trigger’s inactive_strategies CTE can include the same v1_step_concurrency row multiple times when a single INSERT statement creates multiple slots for the same strategy (new_table has duplicates). Deduplicating before FOR UPDATE avoids extra join work/locking overhead and keeps the UPDATE deterministic.

    WITH inactive_strategies AS (
        SELECT
            strategy.*
        FROM
            new_table cs

[github-actions]

⚠️ Optional test failure: The load-deadlock job failed on this PR (optimistic-scheduling=true). This check is non-mandatory and does not block merging, but may be worth investigating. View logs