Chainlink CRE is a platform that combines access to APIs and on-chain processing into workflows. Chainlink CRE workflows limit the number of concurrent executions to prevent too many function calls from occurring simultaneously. This update addresses an issue where two layers managing concurrent execution limits were double-counting the same calls. ⚙️ One call consumed two slots Both the WASM module executing the workflow program and the execution engine processing the calls had mechanisms to track concurrent execution counts. Previously, both layers referenced the same management pool, causing each call to consume two slots from the same pool. As a result, slots were consumed at a higher rate than actual calls, leading workflows to reach their configured limits prematurely. 🔧 Separated management slots for WASM and execution engine After the update, a dedicated pool has been created for the WASM module, isolated from the execution engine’s pool. Each call now uses one slot in the WASM pool and one slot in the execution engine pool—but these are counted separately, eliminating double-counting of the same slot. Both pools still apply the same configured value for maximum concurrent executions. This is not a change that raises the upper limit or removes restrictions on one side; it is a correction to ensure accurate counting across multiple layers. 📊 Monitoring and cleanup processes also adjusted The new WASM-side pool does not include a metrics counter, preventing duplicate monitoring values from being generated under the same configuration setting. However, both pools are now included in workflow cleanup and finalization procedures to ensure no managed resources are left unprocessed after separation. The key outcome of this change is the correction of double-counting in concurrent execution metrics. No improvements in processing time or throughput have been demonstrated; this change should not be interpreted as doubling performance. It is best understood as a fix to align the configured limit with the actual counted number of calls, clearly defining the scope of this update.