Started Seneca Rocks but stopped after 2nd interval due to work. It shows as completed on the app, but has not uploaded to the Web calendar as completed, nor did it get sent to Strava. Manually choosing re-sync caused it to appear ok in the calendar and Strava.
When I click analyse online, I get this error in the Edge Chromium Beta
Server Error in ‘/’ Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a “web.config” configuration file located in the root directory of the current web application. This tag should then have its “mode” attribute set to “Off”.
`
`
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the “defaultRedirect” attribute of the application’s configuration tag to point to a custom error page URL.
Hey there - this isn’t really a bug but a UX suggestion.
In this version, the screen dims and the interval summary pops up for 10 seconds at the end of each interval. In shorter/microburst intervals, this means that the screen stays on those interval summaries for a large percentage of the time and it can be really distracting from seeing what the current power number and target are. It’s not an issue to me for longer intervals, but for 15-30 second microbursts, it’s really distracting.
Hi @kitenski, thanks so much for reporting these issues!
To help us dig into these reports a little easier, can you please let us know what version of TR Beta you’re running? You can find the version number under the ‘Support’ tab, then on the lower right side of the app window:
Hey TR Team, app doesn’t show green bar at top to show update available even though .36-beta should be available. Tried restarting and refresh and waiting 10 minutes. Been similar with previous updates not being showing very quickly.
Really just an FYI to help improve a great product.
Someone pointed this out earlier in the thread (no worries, it has gotten super long) and I think our design team is still in talks about how we want to proceed with it. I can totally see how the constant dimming/brightening during microburst workouts could be distracting!
Hi @getbrem! Sorry about that wait - we’ve had a couple of users report not seeing the green update banner appear for 15+ minutes. We’ve alerted the developers to this issue and we’ll post an update once we hear something about this.
Looking at the logs, I’m seeing a dropout. That was causing some really large wattage offsets that the trainer was trying to make up for. There should be some protections in place to prevent that from happening. They may need to be more robust. I can test this next week.
Did you get this error before or after the ride uploaded? I could see how you would get a runtime error trying to view a ride that hasn’t actually been pushed. Kinda stumped on this one, will definitely need to test out for myself.
Thinking about it now, I agree. Seems like the red has a “reject” connotation. Adding this to the discussion with our Design team. Thanks for the feedback.
There’s a 60-second timeout that happens during calibration but I believe it should be ignored on success. Gonna test this one out on Monday. Sorry that happened!
For me it seems about 5-10 seconds from the dialog reporting success to the timeout message. I think 60 seconds from completion would be fine, and auto-accepting successful calibrations makes sense too.
hi, windows desktop connected via ant - not a major bug but calibration spinout keeps giving a failure notice. Normally takes 3-4 attempts before i get a clean calibration.
I went and continued the ride hours later and it picked up where I left off, so perhaps it is expected behaviour to not sync it to strava etc? If so I’d suggest an option when clicked End to say would you like to save and sync, or “Resume Later” and not upload?
Analyse online also appears to be working this morning!
I’d suggest to reproduce is end a workout before it’s finished!
First (might not be a specific issue with the app), in the 4th interval, I took a backpedal break. When I started again it seemed to be overcompensating and making me put out too much power. I had to take another break and start again before it settled down.
Second, after the backpedal break, the “workout started” text was stuck on the screen in minimal mode and wouldn’t go away until I expanded the window and returned to minimal again:
