Time: June 4, 2024, 10:05 p.m.

Status: Resolved

Update: Our team has deployed a fix for the demo session data pipeline, and Insights functionality has been fully restored. Rest assured, all demo session data was captured before and during the incident, and it is now flowing through to Walnut Insights and Integrations. Thank you for your patience as our team worked to resolve this issue.

Time: June 4, 2024, 8:45 p.m.

Status: Identified

Update: We have identified the root cause of the demo session data delays, and our team is implementing a fix. We expect the demo session data pipeline to be restored shortly.

Time: June 4, 2024, 7:40 p.m.

Status: Identified

Update: We are continuing to work on a fix for this issue.

Time: June 4, 2024, 7:39 p.m.

Status: Identified

Update: Our team has identified an issue where processed demo session data is not appearing in Insights. Demo session data is delayed. All Insights, integrations, webhooks, and email notifications are affected. Our team is working diligently to identify the root cause and implement a fix. We will continue to update with ongoing developments.

Time: April 26, 2024, 8:53 p.m.

Status: Resolved

Update: Version 1.6.42 of the extension is now live and available for download. This version resolves all issues surrounding version 1.6.41. If your extension has not already auto-updated, please update it to the latest version via the Chrome Web Store. Thank you for your patience as our team worked to resolve this issue.

Time: April 26, 2024, 8:02 p.m.

Status: Resolved

Update: Version 1.6.42 of the extension is now live and available for download. This version resolves all issues surrounding version 1.6.41. If your extension has not already auto-updated, please update it to the latest version via the Chrome Web Store. Thank you for your patience as our team worked to resolve this issue.

Time: April 26, 2024, 5:37 p.m.

Status: Identified

Update: Our team has successfully identified the root cause of the disruption, and a long-term solution is in progress. This solution will be available in version 1.6.42 of the extension. Users experiencing issues with version 1.6.41 can resolve them by uninstalling and reinstalling the extension. Our team is committed to keeping you informed, and we'll notify you here as soon as version 1.6.42 is available. Thank you for your patience and understanding.

Time: April 26, 2024, 2:15 p.m.

Status: Identified

Update: We are continuing to work on a fix for this issue.

Time: April 26, 2024, 2:13 p.m.

Status: Identified

Update: We are continuing to work on a fix for this issue.

Time: April 26, 2024, 2:11 p.m.

Status: Identified

Update: Our team has identified an issue with version 1.6.41 of the Walnut extension tool and are working diligently to implement a fix. The issue can be resolved in the short term by removing and reinstalling the extension. We will continue to update with ongoing developments.

Time: April 23, 2024, 4:53 p.m.

Status: Resolved

Update: After a thorough monitoring period, we have verified that the fix has fully resolved the disruption. All components, including web analytics and custom event tracking, have been restored to their expected functionality. We would like to express our sincere gratitude for your patience and understanding during this incident. We appreciate your continued support, and we apologize for any inconvenience caused by the disruption. Our team remains committed to providing reliable and high-quality services, and we will continue to work diligently to prevent similar incidents from occurring in the future.

Time: April 23, 2024, 4:36 p.m.

Status: Monitoring

Update: The fix for the misconfiguration issue in our data processing pipeline has been successfully deployed across our infrastructure. We are closely monitoring the situation to ensure that the fix has fully resolved the disruption and that analytics data collection and processing are operating normally.

Time: April 23, 2024, 3:58 p.m.

Status: Identified

Update: Our engineering team has identified the root cause of the issue. The disruption was caused by a misconfiguration in one of our data processing pipelines, leading to a bottleneck in the analytics data ingestion process. Our team is currently working on implementing a fix to resolve the misconfiguration and restore the normal data flow. We expect the fix to be fully deployed within the next 30 minutes.

Time: April 23, 2024, 3:53 p.m.

Status: Investigating

Update: We are currently experiencing a partial disruption in our analytics data collection system. As a result of this incident, some of our customers may experience incomplete or delayed analytics data collection and reporting. Our team is working diligently to resolve this issue as quickly as possible. We apologize for any inconvenience caused by this disruption and appreciate your patience. Walnut Incident Response Team

Time: March 18, 2024, 10:55 a.m.

Status: Resolved

Update: This incident has been resolved.

Time: March 18, 2024, 9:22 a.m.

Status: Identified

Update: Dear Users, We want to inform you of an ongoing issue identified in our platform, stemming from a recent code update. This issue affects the completeness of data related to several key features, including Insights, Demo View Emails, Webhooks, and Lead Form Analytics. <b>What is affected?</b> - <b>Insights</b>: There may be missing data points that affect overall analysis and reporting. - <b>Demo View Emails</b>: The affected emails might lack certain engagement metrics. - <b>Webhooks</b>: Some events might not trigger webhooks, leading to missing data downstream. - <b>Lead Form Analytics</b>: The analytics may not fully capture all interactions, affecting metrics like completion rate and session duration. <b>What does this mean?</b> While we are still capturing sessions associated with these features, the data might not fully represent all user interactions. Specifically, metrics related to the completion rate and the duration of these interactions might be inaccurately reported. <b>What are we doing?</b> Our engineering team has already identified the cause and is working diligently on a fix. We prioritize the integrity of your data and are committed to resolving this issue promptly. <b>What can you do?</b> Please be aware that data for the affected features might not be complete during this period. We recommend waiting for our update before making significant decisions based on the data from the aforementioned features. We apologize for any inconvenience this may cause and thank you for your understanding and patience. We will provide updates as soon as more information becomes available or upon resolution of the issue. For any immediate concerns or additional support, please contact [email protected]. Thank you for your attention to this matter.