A Collection of Programming Tools

[MikeMullany]

Closed and re opened app. Re built entire plan. Same message.

[Shaun]

Sorry @Hanley. My plan shows. But when you hit build this pops up. “We could not reach your training g data. Check your connection and try again”’

I also had this issue. I am using Autopilot with Train When Ready selected. I had 2x missed sessions from around a week ago that I just removed and then it seemed to work.

[Hanley]

Closed and re opened app. Re built entire plan. Same message.

Can you try one more timr?

Fingers crossed

[MikeMullany]

Not ready to train yet, but preview is showing my main lifts and accessories, so I think it’s good.

[Hanley]

Not ready to train yet, but preview is showing my main lifts and accessories, so I think it’s good.

Sweet. Lemme know if anything is still fucked

[Shaun]

For the check-in, when inputting soreness levels, can you add a specific "low back" location that will influence squatting and deadlifting volumes?

[MikeMullany]

@Hanley. Stopped using autopilot and have been building my own blocks with a focus on strength. I love the sessions it’s been spitting out. Maybe I’m doing something wrong, or not understanding but I thought I built a 3 week block and it seemed to have ended the block after one week. I built a second block , and thought I made a two week block, and it may have picked up the last week of the first block as it started on session 4 of 6. Again, not sure if this is a bug, or something I’m not understanding while building. I was using an upper/lower split, and I believe 3 sessions per rolling 7 days the first block, and 4 the second block, and the train when ready option.

Also, on strength cluster sets, I’m pretty sure the recommended rest didn’t show until I completed the first cluster.

[Hanley]

@Hanley. Stopped using autopilot and have been building my own blocks with a focus on strength. I love the sessions it’s been spitting out. Maybe I’m doing something wrong, or not understanding but I thought I built a 3 week block and it seemed to have ended the block after one week. I built a second block , and thought I made a two week block, and it may have picked up the last week of the first block as it started on session 4 of 6. Again, not sure if this is a bug, or something I’m not understanding while building. I was using an upper/lower split, and I believe 3 sessions per rolling 7 days the first block, and 4 the second block, and the train when ready option.

Also, on strength cluster sets, I’m pretty sure the recommended rest didn’t show until I completed the first cluster.

For the check-in, when inputting soreness levels, can you add a specific "low back" location that will influence squatting and deadlifting volumes?

@Shaun and @MikeMullany

I've got the features and bugs fixed....just waiting for a quality review to push to to the production app.

[Shaun]

@Hanley, when trying to build today's session I get the following error: "This block's schedule could not be read. Reload and try again."

I have signed out and back in again and still get the same issue.

[Hanley]

@Hanley, when trying to build today's session I get the following error: "This block's schedule could not be read. Reload and try again."

I have signed out and back in again and still get the same issue.

Hmm. Can you give it one more try? We've been doing a ton of work in the database.

[Shaun]

@Hanley, when trying to build today's session I get the following error: "This block's schedule could not be read. Reload and try again."

I have signed out and back in again and still get the same issue.

Hmm. Can you give it one more try? We've been doing a ton of work in the database.

I inserted a rest day (I'm using autopilot) and now there no longer seems to be the option to build today's session.

[Shaun]

It's working today.

[MikeMullany]

@Hanley Built another new block. Did the first session, then it jumped to session 10 of 12. Sessions it’s building are great though.

[Hanley]

@Hanley Built another new block. Did the first session, then it jumped to session 10 of 12. Sessions it’s building are great though.

Fuuuuuuuuck. Okay. Okay. Will fix.

[Shaun]

@Hanley the app's down for me. I get the following message: "Your training data could not be loaded. Retry to load your latest training data." Retry doesn't do anything.

[Hanley]

@Hanley the app's down for me. I get the following message: "Your training data could not be loaded. Retry to load your latest training data." Retry doesn't do anything.

Roger. We've been doing a pretty major overhaul to the database. Might just be a temporary thing. I'll check

[Ryaan]

Hey guys - sorry for the outage. That's on me. Doing a pretty major overhaul and accidentally took down the site. Fix inbound now.

[Ryaan]

We're back @Shaun and others. Apologies for the downtime.

[MikeMullany]

@Hanley @Ryaan. Sorry to be annoying. Just finished what should have been my last session of the shortened block before you guys did your thing. It won’t let me save that last session, and therefore can’t build my next block as it’s telling me my last block is not complete.

[Ryaan]

@Hanley @Ryaan. Sorry to be annoying. Just finished what should have been my last session of the shortened block before you guys did your thing. It won’t let me save that last session, and therefore can’t build my next block as it’s telling me my last block is not complete.

Damn - fix inbound.

Not annoying, thanks for these reports everyone and for your patience as we monkey with things.

I'm sorry to say we're probably going to have a period of some instability over the next few days. We're doing a huge port of the DB architecture in prep for starting to write native mobile apps, and there's a lot of cleaning house we're need to bite the bullet and do right now to go from "not exactly stable beta software" to "the foundation the app will run on for a few years". It's high risk and going to mess with things in the short term, but hopefully once it settles down the app will be a lot more stable in development moving forward.