Sympa HR incident
Performance Degradation - Delays in Reporting Data Updates
Sympa HR experienced a minor incident on April 1, 2026 affecting Reporting and Integrations, lasting 2h 2m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Apr 01, 2026, 07:57 AM UTC
We are currently experiencing delays in data appearing in reporting after updates are made in Sympa (for example, when adding new employees or modifying existing data). At the moment, updates may take several minutes, and in some cases up to approximately one hour, to be reflected in reports. The system is otherwise operating normally, and no data is being lost. Our team has identified the root cause and is currently deploying a fix to restore normal performance. We will provide updates as the deployment progresses. Your Sympa Team
- monitoring Apr 01, 2026, 08:37 AM UTC
Dear Customer, A fix has now been deployed to address the delays in reporting data updates. We are currently monitoring the situation as performance stabilizes. While improvements should already be visible, it may take several hours for the system to return fully to normal. During this time, you may still experience delays in data appearing in reports after updates are made. We will continue to monitor closely and provide further updates. Your Sympa Team
- resolved Apr 01, 2026, 10:00 AM UTC
The delays affecting reporting data updates have now been fully resolved. System performance has returned to normal, and new or updated data is appearing in reports as expected. We will continue to monitor to ensure stability, but no further impact is expected. Thank you for your patience. Your Sympa Team
- postmortem Apr 13, 2026, 12:22 PM UTC
**What happened** On April 1, 2026, starting at 09:07, customers experienced delays in seeing their data after saving. **Why it happened** The issue was caused by a limitation in the system responsible for handling background processing. It reached its capacity and could not process new and ongoing operations efficiently. In addition, the system did not release memory quickly enough during high usage, which caused delays before saved data was applied. **What we did** We took the following actions to resolve the issue: * Improved how the system releases resources, making it more responsive during high usage * Optimized memory usage to improve overall stability These changes were fully implemented by 10:43, and the disruption was fully resolved by 12:34.