Staffbase Status

Resolved: The issue is resolved. We apologize for the inconvenience this has caused. Please get in touch with us at [email protected] in case you're still having any problems. We’re happy to help!

Monitoring: A fix has been implemented to resolve the issue affecting CSV imports that included commas, quotation marks, or line breaks. Imports should now work as expected again.

We will continue to monitor the behavior to ensure everything is functioning correctly.

If you notice any remaining issues or need assistance, please don’t hesitate to contact our support at [email protected]

Identified: Affected feature: CSV Import

We’re currently seeing issues with the CSV import in cases where entries include commas, quotation marks, or line breaks. These special characters can lead to incorrect or failed imports.

Our teams have identified this behavior and are already working on a fix. We will continue to monitor the situation and share updates as soon as possible.

We apologize for the inconvenience this may cause. If you have any questions or need support with a specific import, feel free to reach out to us at [email protected].

Resolved: The issue is resolved. We apologize for the inconvenience this has caused. Please get in touch with us at [email protected] in case you're still having any problems. We’re happy to help!

Monitoring: A fix has been implemented to resolve the issue affecting CSV imports that included commas, quotation marks, or line breaks. Imports should now work as expected again.

We will continue to monitor the behavior to ensure everything is functioning correctly.

If you notice any remaining issues or need assistance, please don’t hesitate to contact our support at [email protected]

Identified: Affected feature: CSV Import

We’re currently seeing issues with the CSV import in cases where entries include commas, quotation marks, or line breaks. These special characters can lead to incorrect or failed imports.

Our teams have identified this behavior and are already working on a fix. We will continue to monitor the situation and share updates as soon as possible.

We apologize for the inconvenience this may cause. If you have any questions or need support with a specific import, feel free to reach out to us at [email protected].

Resolved: The issue is resolved. We apologize for the inconvenience this has caused. Please get in touch with us at [email protected] in case you're still having any problems. We’re happy to help!

Monitoring: A fix has been implemented to resolve the issue affecting CSV imports that included commas, quotation marks, or line breaks. Imports should now work as expected again.

We will continue to monitor the behavior to ensure everything is functioning correctly.

If you notice any remaining issues or need assistance, please don’t hesitate to contact our support at [email protected]

Identified: Affected feature: CSV Import

We’re currently seeing issues with the CSV import in cases where entries include commas, quotation marks, or line breaks. These special characters can lead to incorrect or failed imports.

Our teams have identified this behavior and are already working on a fix. We will continue to monitor the situation and share updates as soon as possible.

We apologize for the inconvenience this may cause. If you have any questions or need support with a specific import, feel free to reach out to us at [email protected].

Postmortem: ## Summary

As our investigation of the incident is complete, we would like to provide you with more detailed information about the incident that occurred on January 16, between 03:00 p.m. and 10:20 p.m. (CET), leading to issues with the visibility of analytics data for sent emails.

What happened

The incident was triggered by a database migration that inadvertently impacted the synchronization of mail analytics. This caused a delay in the processing and display of performance metrics for emails sent during the affected window. Once the root cause was identified, our engineering team implemented a fix to restore data flow. We have confirmed that no data was lost; all analytics tracked during this period were successfully backfilled and are now visible.

Impact

Between 03:00 p.m. and 10:20 p.m. (CET), users were unable to view analytics for emails sent out during this window. While the emails were delivered successfully and recipient interactions were still being tracked by our systems, the data was not being rendered in the user interface.

Future improvements

To prevent similar occurrences and ensure system stability during maintenance, we will implement a different strategy for updating data to ensure a more performant migration and a reasonable update duration.

Thank you for your patience and understanding while we work to improve our services and prevent future incidents. If you have any questions or concerns, please do not hesitate to reach out to our customer support team at [email protected].

Resolved: The issue is resolved and analytics are shown again for the affected mails. We apologize for the inconvenience this has caused. Please get in touch with us at [email protected] in case you're still having any problems. We’re happy to help!

Identified: We have identified the root cause for analytics not being shown for emails send out in the last 6 hours (starting 3:00 PM CET) and will now take steps to fix the issue. No data is lost and the analytics for the affected mails will be available again after this incident is resolved.