Historia awarii Validic

This is less of reporting an issue and more for noting a fix for something Validic noticed about Apple iOS 26 and summary records. Apple has always surfaced old summary records as new records in their HealthKit api as part of their housekeeping. In iOS 26, it appears this can happen much more frequently. Apple has acknowledged this is a bug in iOS 26. In versions older than Legacy iOS Native 1.18.0, in certain situations, the SDK would process that old record and then query every summary record since then. This creates a large volume of redundant summary records and slows the speed at which new data is ingested for users. More information about this is on this KBA: https://help.validic.com/space/VCS/4957044737/Apple+Health+Summary+Record+Volume+Improvements Clients using the Apple Health/HealthKit module in the Validic SDK are encouraged to update to Legacy iOS Native 1.18.0 to mitigate this and have the best performance they can with our integration with the HealthKit API If you or your team has any questions about the information above or in the linked KBA, open a ticket with Validic technical support by emailing [email protected]

We are going to close this status page as it was more of an FYI for our clients than reporting an internal issue. If there are any questions about the below KBA, then reach out to the technical support team at [email protected] https://help.validic.com/space/VCS/4957044737/Apple+Health+Summary+Record+Volume+Improvements

Overnight, Polar had an update to its system due to new EU regulations. Due to this, end users will need to open the Polar app on their phone and accept the new terms to allow for data sharing with third-party applications like the Validic ecosystem. Until an end user takes that action, data will not be shared with third-party applications, including Validic. Clients using Polar need to message end users to let them know to take this action to ensure continued data syncs from the Polar API to the Validic servers. Information on the EU regulations that went live: https://iapp.org/news/a/eu-data-act-all-your-threshold-questions-answered Polar Status page on this: https://status.polar.com/ If a client using Polar has questions about this, send in a ticket to Validic technical support by emailing [email protected]

We appreciate the clients who have reached out to your users to request that they take this action in the Polar application to allow data to flow. We have not seen a great drop in the number of errors related to the need for the end users to take this action. Validic will be unable to pull data from the Polar API until users accept the new terms, including the update for the new EU regulations. Polar status page: https://status.polar.com/incidents/wn2cgh4q79pr Information on the EU regulations that went live: https://iapp.org/news/a/eu-data-act-all-your-threshold-questions-answered If a client using Polar has questions about this, send in a ticket to Validic technical support by emailing [email protected]

We are seeing the rate of errors for Polar trending down, but end users should still be encouraged to take the following action, as that will be the only path to resolution for the user's data being made available in the Polar cloud. It appears there are still a lot of users who haven't taken that action yet. Polar had an update to its system due to new EU regulations. Due to this, end users will need to open the Polar app on their phone and accept the new terms to allow for data sharing with third-party applications like the Validic ecosystem. Until an end user takes that action, data will not be shared with third-party applications, including Validic. Clients using Polar need to message end users to let them know to take this action to ensure continued data syncs from the Polar API to the Validic servers.

We have seen the number of errors continue to trend down, but we are still seeing errors for users who haven't taken the action of accepting the new Polar terms and conditions in the Polar application. We've created the following KBA regarding this. We urge our clients who depend on Polar data to be in communication with their end users to ensure you still receive Polar data from them. Since there is no action Validic can take to resolve this for the end user, we will be closing this status page. https://help.validic.com/space/VCS/4940169227/Polar+Terms+&+Conditions+Update+Required+for+Data+Syncs

We've identified an issue causing increased errors when syncing nutrition data from Fitbit, resulting in "500 Internal Server Error" entries appearing in client logs. The issue is due to recent unexpected changes in Fitbit's nutrition data format. Our engineering team is actively working on an update to handle these changes. We've reached out to Fitbit for clarification and are monitoring the situation closely. We will provide further updates as new information becomes available. Thank you for your patience.

Fitbit made an adjustment on their side and the issue is fully resolved

Validic is investigating possible issues with the delivery of data from Fitbit. As a result, you may see delays in receiving user data from Fitbit users and users may see issues when trying to sync to Fitbit. We will provide updates here when they are available.

Data is flowing successfully after a period where it wasn't. We're monitoring as the data catches back up.

Data continues to flow as expected. This issue is resolved.

Validic is investigating possible issues with the delivery of data from Fitbit. As a result, you may see delays in receiving user data from Fitbit users and users may see issues when trying to sync to Fitbit. We will provide updates here when they are available.

Fitbit has reported that they are experiencing an outage at this time. The Validic team will continue to monitor. Fitbit is tracking this issue here: https://status.fitbit.com/

Fitbit has updated their status page noting that the issue is resolved. Validic is seeing data delivery start to return to expected levels. There may still be some delays while we receive any data that was not received during the outage. We will continue to monitor and provide updates here as they are available.

Fitbit performance has been stable at the expected levels.

Validic is currently investigating possible issues with the Validic API. As a result, you may see delays or errors when attempting to make calls to the API to access data or manage users. We will post updates here as they are available.

We have identified the issue and are working on a fix and monitoring all systems. More updates will be posted here as they are available.

The Validic team has address the issue and all systems are caught up. We will continue to monitor to ensure that no new issues come up.

This incident has been resolved.

Google is currently experiencing issue with their authentication services. This can affect any service that uses Google authorization for users to log in, including Fitbit. This is not a Validic issue. Validic will monitor this issue and provide updates here as they are available. Google is tracking this issue here:
https://status.cloud.google.com/regional/americas

We are also seeing possible delays in the delivery of Fitbit user data as a result of this outage.

We are continuing to investigate this issue.

As an update here, Validic is finding that this outage is potentially affecting the delivery of data from more sources than just Fitbit. You may see delays receiving user data from potentially any data source at this time. Validic is continuing to closely monitor this.

This incident has been resolved.

Validic is investigating possible issues with the delivery of data from Fitbit. As a result, you may see delays in receiving user data from Fitbit users and users may see issues when trying to sync to Fitbit. We will provide updates here when they are available.

Fitbit has confirmed that they are reporting a service outage via their status page. Validic will continue to monitor. https://status.fitbit.com/

Fitbit has reported that this issue is resolved. Validic will continue to monitor as we do see data flow gradually returning to normal.

This incident has been resolved.

Validic is currently investigating an issue where users are seeing an error when trying to navigate to the iHealth authorization page via the Validic marketplace. We are also investigating possible delays in the delivery of data from iHealth. As a result, users will not be able to connect to iHealth and you may see delays in receiving data from connected iHealth users. We will update this post as new information is available.

iHealth data flow appears to be returning to more normal levels. The iHealth authorization page also has been loading as expected and users have been able to connect their iHealth accounts via the Validic Marketplace. We will continue to monitor for stability.

This incident has been resolved.

Validic is currently investigating a possible issue where pages in the Support Portal at https://help.validic.com may not be loading for some users. We will provide updates here as they are available.

Page loads are returning to the expected behavior in the Validic Support Portal. We will monitor for stability.

This incident has been resolved.

As of late August 2024, Fitbit has adjusted their algorithm for calculating metrics such as calories burned, distance, and times in heart rate zones. These changes may result in metric values that are much higher or lower than anticipated. Usually, these sorts of values can be explained by the personal information the user has stored in their Fitbit user profile. Why are calories burned, distance, and/or time in heart rate zones values different than I expect? Fitbit devices estimate your users’ calories burned by combining their basal metabolic rate (BMR) with their activity data. BMR is calculated using the Fitbit profile information, including height, weight, sex, and age. It's important to have users make sure that this information is entered accurately in their Fitbit account, as it significantly impacts the calorie calculations. If their device tracks heart rate, this data is also incorporated, especially when estimating calories burned during exercise. To ensure the most accurate calorie burn, distance, and time in heart rate zone estimations: 1. Have the user verify and update their Fitbit profile: Confirm that their height, weight, sex, and age are correct in their Fitbit account settings. See https://support.google.com/fitbit/answer/14236616?sjid=16936490723788951099-NA 2. Utilize the Exercise app: For activities like spinning or yoga where step count might not accurately reflect intensity, the user should consider using the Exercise app on their Fitbit device to track workouts and capture real-time heart rate data. 3. Consider GPS tracking: If the user frequently engages in activities where their arm movement is restricted, such as pushing a stroller or holding a dog leash, using GPS tracking can improve distance and calorie burn calculations. If users continue to have trouble tracking these metrics, please have them reach out to the Fitbit community for assistance: https://community.fitbit.com/t5/Community/ct-p/EN

Fitbit has communicated to us that they have resolved all open issues around their application and their API syncing. We are resolving this status page and appreciate everyone's patience with this. It has been challenging as there were things out of our control with changes to the Fitbit API and Fitbit issues that required their attention. If you encounter scenarios where you see a cloud-connected Fitbit user seeing different things in what is showing in the user's Fitbit application and what is in the Validic API, Validic technical support is here to assist. We do request that you do the following before writing in though. 1. Work through the steps on this page with the affected user: https://help.validic.com/space/VCS/3480453131/How+to+troubleshoot+Inform+issues 2. If working through those steps doesn't resolve the issue then open a ticket with our team and share the troubleshooting steps you have taken along with screenshots of the user's Fitbit application that shows a difference in what is in the Inform API. Don't forget to share the Validic ID and Org ID. Validic technical support will need that information to fully investigate the scenario for the user.

Validic is investigating possible issues with the delivery of data from Fitbit. As a result, you may see delays in receiving user data from Fitbit users and users may see issues when trying to sync to Fitbit. At this time, the queue is catching up, but there still may be slight delays in the delivery of Fitbit data.

This incident has been resolved.

Validic is investigating possible issues with the delivery of data from Fitbit. As a result, you may see delays in receiving user data from Fitbit users and users may see issues when trying to sync to Fitbit. We will provide updates here when they are available.

Fitbit data is again flowing as expected. We will continue to monitor for stability.

Fitbit data continues to flow as expected. This issue is resolved.

Recently, Strava announced that they would be launching a new Developer Program for all users of their API data. Their planned cutover to that new program is March 4, 2024. Validic has been aware of this change and has been working closely with Strava to update all Validic developer credentials in an effort to have a seamless transition. There is no action for you or your Strava users. No interruption of data delivery is expected. This status page is simply to inform you that this change will be happening behind the scenes. Should you see any issues with user connections or data flow with Strava after March 4, 2024, please contact the Validic Support Team via https://help.validic.com

As part of the transition to this new developer program, Strava set the number of allowed athletes to a high number for all Validic developer accounts. We have discovered that some Validic orgs were not set to a high enough number to allow the addition of new Strava users. Validic is working directly with Strava to resolve this.

Strava data and user connections have been consistent and as-expected since this change so we will close this status page. If you do happen to see any issues with Strava users or data please contact the Validic Support Team via https://help.validic.com

Validic is investigating possible issues with the delivery of data from Fitbit. As a result, you may see delays in receiving user data from Fitbit users and users may see issues when trying to sync to Fitbit. We will provide updates here when they are available.

The Fitbit integration appears to be functioning as designed at this point. We're monitoring the situation to ensure it is completely resolved.

This issue if fully resolved.

Earlier today there was a delay in processing Validic API data for approximately 30 minutes. Data processing has since caught up and yo should not be missing any data.

Validic is investigating a possible issue where users may experience errors when attempting to authorize Polar in the Validic marketplace. As a result, some users may not be able to successfully connect to Polar. We will provide updates here as they are available.

Validic is still investigating possible solutions to the Polar authorization issues. We will update this status as more information becomes available.

This incident has been resolved.

Fitbit has reported that users who have connected their Fitbit accounts via Google may not be able to log in or see their Fitbit data when logged in. As a result, you may not see some Fitbit user data in the Validic API while Fitbit works to resolve this issue. Validic will continue to monitor this and provide updates here when they are available.

Fitbit has resolved this issue.

Validic is investigating possible issues with the delivery of data from OneTouch. As a result, you may see delays in receiving user data from OneTouch users and users may see issues when trying to sync to OneTouch. We will provide updates here when they are available.

This issue appears to be related to a widespread AWS issue. We are continuing to monitor.

OneTouch data is starting to flow as expected. Validic will continue to monitor.

This incident has been resolved.

Validic is investigating possible issues with the delivery of data from Fitbit. As a result, you may see delays in receiving user data from Fitbit users and users may see issues when trying to sync to Fitbit. We will provide updates here when they are available.

Fitbit data is starting to flow as expected. Validic will continue to monitor.

This incident has been resolved.