Magic buckets 1st fetch gets overriden values, 2nd fetch gets original values

Support
1

If you override the workout for the day by inputting manual XSS low/hi/peak, on the 1st fetch and ride, Magic Buckets gets the overriden values.

If you then save the ride, like at the coffee stop for an hour or whatever, and then start a new ride, Magic Buckets doesn’t get the remainder of the overriden values. It gets the original ride values, with what you’ve already done shown in there.

Today I had an endurance ride on the schedule, I overrode the values to do a ride with lo/hi/peak, and saved the file. Magic Buckets was on the 3 bucket screen. On the second part of my ride day, I was back to the original ride, with the Magic Buckets endurance screen.

Is this the expected behavior? Version 10.8 of Magic Buckets

2

The server should retain the override values for the day and reflect those on the second fetch.
Is it possible you filled the high/peak buckets before the cafe stop?
That would explain a change to the Endurance screen, but the Low XSS target should be the override number you entered for the day.
If the problem repeats I suggest filing a bug report.

3

Sadly no I hadn’t hit the targets. I’m sure I’ll run into this 2 files for the same day kind of thing, and if the problem repeats, I’ll file a bug report.

I just think if you’re stopping for a decent amount of time, just create a second ride instead of pausing it or letting it run.