WK05/TPweb - Please refer to http://wko5.zendesk.com/hc/requests/906838.

After much back and forth working with TP's WK05 customer service, it appears that with the latest upgrade of the health metrics, there are new issues causing Garmin Sync data perhaps not syncing to TPweb and then clearly not syncing from TPweb to WK05.

Stress is an example of this issue. In my data set, Stress would sync from Garmin Connect to TPweb to WK05 without issue, as long as I followed the process of making sure the sync was complete from, a) Garmin device to garmin connect, b) from Garmin connect to TPweb, and c) from TPweb to WK05 via the sync button.

After a long layoff due to various health issues, I returned to the above syncing process and discovered that some, not all, health metrics had stopped syncing.

Using Stress as an example, here's the message I received for customer service —

"We've found that there are two different ways to record Stress in TrainingPeaks: The longer-resident "Stress" field, which has a limited selection of text values (from None to Extreme), and the "Stress Level" field that's an open-ended number entry field. WKO does not have the ability to read the "Stress Level" field, but it can read the "Stress" field. It looks like you are using the "Stress Level" field, which was added to TP from Garmin.

Unfortunately, this metric will not be downloaded to WKO. I hope this helps to clarify things. Please don’t hesitate to reach out with any other questions."

To this response, I provided a response to clarify —

"Consider that I have never specified what field in TP is used; rather, that TP has always synced with Garmin Connect for all health metrics. Something has changed over time with how this process is handled.

Was it Garmin or was it TP?

What ever changed has knock-on effects in the sync as Stress is not the only issue - recall Pulse has also been impacted by the change

Would you guys be kind enough to find out what changed? I am trying to get your softwares to work as advertised. If we can go with that as the original requirement, then instructions on how to achieved complete syncs would be helpful.

An example might be that by resetting the sync, a new method was introduced?"

The customer service person has told me that the only way to track this is to put it into this forum, which implies to me that Peaksware may not fix the sync issue created with updates to the field usage between Garmin, TPweb and WK05.

Goal, I would like TPweb/WK05 to work as advertised. To that end, I request that Peaksware investigate their sync process between Garmin Connect, TPweb and WK05 to resolve the issues.

• reminder - Stress is an example of one that does not work others do not work as well
• unfortunately, in turning over my userid and password to customer service for testing on their platform to uncover the issue, WK05 requires reactivation and there appears to be an operation issue that would cause me to have to rename my computer.

Peaksware, please look holistically at the sync process modifications made in the recent past to re-map your sync from Garmin to TPweb to WK05.

Why? I have many years of data in WK05. I'd like it to be complete.

Other concern: Is Peaksware going to make WK05 obsolete? Please respond on this point as well.