Skip to content

fix: only keep v1_step_concurrency active when it has work#3629

Open
grutt wants to merge 1 commit intomainfrom
fix--only-keep-v1_step_concurrency-active-when-it-has-work
Open

fix: only keep v1_step_concurrency active when it has work#3629
grutt wants to merge 1 commit intomainfrom
fix--only-keep-v1_step_concurrency-active-when-it-has-work

Conversation

@grutt
Copy link
Copy Markdown
Contributor

@grutt grutt commented Apr 16, 2026

Description

CheckStrategyActive was keeping any strategy on the latest workflow version pinned is_active=true regardless of whether any tasks were queued or running. This caused active strategy counts to grow with every deployment, each spinning up a ConcurrencyManager that polled Postgres every 500ms-5s. Strategies are now deactivated when idle and re-activated by the after_v1_concurrency_slot_insert trigger when new
work arrives.

In simpler words, v1_step_concurrency is deactivated if no future work exist.

Type of change

  • Bug fix (non-breaking change which fixes an issue)

Copilot AI review requested due to automatic review settings April 16, 2026 15:31
@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 16, 2026

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

Project Deployment Actions Updated (UTC)
hatchet-docs Ready Ready Preview, Comment Apr 16, 2026 3:34pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant