[bolekk]

Each capability call acquired two slots from the same per-workflow CapabilityConcurrency pool: one in the WASM host (PendingCallsLimiter) and one in the engine. Under bursts, executions holding their first slot could starve each other and hang until the execution timeout.

The WASM host now gets its own pool (WASMModulePendingCalls) with the same limit, so each call takes one slot from each pool.

JIRA: CRE-7294

Deployment Validation

resource_PerWorkflow_CapabilityConcurrencyLimit_usage drops ~2x on upgraded nodes vs. non-upgraded nodes in the same DON, and is never pinned at its limit during bursts.

🤖 Generated with Claude Code

[github-actions]

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[github-actions]

✅ No conflicts with other open PRs targeting develop

[trunk-io]

   

Failed Test	Failure Summary	Logs
Test_CRE_V2_ShardFailoverConfidentialWorkflows	The test failed because the Vault public-key request could not reach quorum, with fewer than the required three matching responses.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs