As understood, Step Group variables become ready and are evaluated just before the Run Step process. This can benefit some processes, but it also leaves a gap where some variables that may be defined within the Step Group are not available for resource allocations within the Steps in the Step Group.

This is counterintuitive to the natural understanding of how Step Groups function and can lead to confusion as a defined value is not respected within the resources contained within the step (e.g. limits specified in a build stage, utilizing the StepGroup Variables)

While there is a workaround and there will be documentation around this behavior, we fear this error in interpretation will re-occur with less-experienced Harness users.