WindyMiller Yeah, the way to look at it or understand the logic we've implemented is this:
1) We check all slots you have selected, inside or outside agile charge windows.
2) When we run the auto-population, we then apply the cheapest x (in your case 12) slots for charging.
We then combine all slots together and ignore duplicates, effectively a Union on the sets.
This works for the common scenarios where users may select the additional extra slot in a charge window - but may not be the cheapest, as well as the scenario where additional slots are selected outside the charge window.
The reselection of the 22:00 slot seems weird as that is not one of the cheapest 12, but the 00:30 and 01:00 slot are, so we'd expect them to be reselected based on our logic above. In fact, I'm unsure why you said you had to unselect the 22:00 slot in the first place?
Thanks for the details, we'll do some troubleshooting.
