This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ConnectIQ charts no longer appear on Connect Web

IQ Data Fields charts no longer appear on the website's activity page, while they are working in the iOS app.

Connect IQ Summary works as usual, but no charts are displayed for new and older activities.

  • Former Member
    0 Former Member over 2 years ago in reply to dioveht
    The only common DF is Stryd Zones.
    • that is not enough to debug
    • you also need to find out what is used together with the common denominator Wink
  • Former Member
    0 Former Member over 1 year ago

    I have the same issues. Did you ever resolve this?

  • No, still can't see ConnectIQ charts on Connect Web. Really disappointing...

  • That usually happens when there is a problem with one of the IQ app, or one of its graphs. If you use multiple CIQ apps, try disabling them all, and then adding one at a time, to localize the problem. You can test it with just a brief several seconds long dummy activity, no need to do true runs or rides.

    You can also check the folder //GARMIN/Apps/LOGS/ - there might be a debug log revealing some clues

  • As per the discussion in this thread (which you participated in), the problem is that the CIQ data field graphs appear in the Connect app but not the website, so it's unlikely it's a problem with one of the CIQ data fields on the device.

    It's more likely that this is a problem on Garmin's end, which we have seen many times over the years. (CIQ graphs appear on the website and not the app or vice versa.)

  • Yes, the non-displaying of the graph in GC web is certainly a problem in GC Web, since it should not stop parsing even if there is an issue with one of them. However, you may be still able to localize the problem (in case you use multiple CIQ apps) by disabling them all and then re-enabling them individually.

    At least you can find whether it happens only when they are combined together, or also standalone. It the problem can be isolated to a single app, the developer of the app may be perhaps able to provide some more help with the debugging.