This error was solved, and wasn’t caused by the new harmonizeValues parameter. If you come across a similar problem when using Sentinel-2 L1C collections, it’s important to check the advanced parameters in your layer configurations, as over time, features and parameters may no longer be supported so it’s always good to check the latest documentation and check your requests are using all the latest features so you can get the best possible product
For example, in this case, an old depreciated parameter called atmosphericCorrection was used as a parameter. This is no longer supported, so may do strange things to the results of your requests! If you wish to use atmospherically corrected Sentinel-2 images, we recommend using Sentinel-2 L2A collections instead.