Generated new plan, very slow ramp-up even though I have been regularly doing workouts for the past couple months

Bug Reports
1

Like the title says.

I put some restrictions on the plan generation like ‘dont’ create run workouts longer than 35 minutes for February’, and it might have taken that as ‘don’t create run workouts if the ML says it should be longer than 35 minutes’ rather than ‘if it should be longer than 35minutes, cap at 35minutes and still generate’

I believe the relevant plan request restrictions are:

  • Running Workout generation:
    • I will be using a treadmill for runs until April, do not create any workouts with intervals less than 30 seconds until then
    • Do not create any run workouts longer than 35 minutes in February
    • Do not create any run workouts longer than 45 minutes in March

Screenshot(s):

image
image1366×809 46.6 KB

image
image1370×835 43.9 KB

image
image1343×555 27.9 KB

2

Still a problem? Looks like your new plan in the other post about missing strength workouts has more running workouts. Might be related to the recent backend agent degradation.

3

In my other post when I removed the request to limit time of running workouts it did create running workouts, but without the strength workouts (also this one failed to create strength workouts too).

Consider it ‘confirmation’ that plan prompting for run length resulted in no run generation because when the prompt request was removed it started generating again.

1 Like
4

Yeah, I generated a new plan today with this request, I tried to simplify things a bit:

Starting with run workouts 35 minutes long, increase duration by at most 5 minutes per week.

It generated:

  • This week: 30m run workouts
  • Next week: 45, 40 40, 35
  • Week after: 35, 50

I’ll go back to my old request in the prompt.

5

I tried my old prompt, the next two weeks had 5 run workouts scheduled (two this week, 4 next week). The week of:

  • March 9th had 1 run workout
  • March 16th had 1 run workout
  • March 23rd had 1 run workout
  • March 30th had 2 run workouts.

image
image1309×810 53.4 KB

image
image1328×812 53.7 KB

6

Hm… I think the low run count is it being conservative and putting your injury history first, since there are lots of other workouts too (ride, strength).

It looks like the backend agent is deleting some of your runs of your ML plan created before the agent has a go/what the agent uses as input

7

I removed the restrictions and it generated a much more sensible plan. I’ll just adapt it using the chat.

1 Like