Circular dependency with perGroupFunction and resourceConcurrency
sweepy84 opened this issue · 2 comments
sweepy84 commented
There seems to be a bug in how resource concurrency is implemented with perGroupFunction strategy or custom splitting using stacks-map.js.
It is very easy to replicate - just use those 2 features together.
sweepy84 commented
Btw this happens also with custom splitting strategy (not just perGroupFunction) and possibly other scenarios. When resources are moved to a nested stack and resourceConcurrency is on.