Is Sympa HR down?

Dear Customers, We are currently investigating degraded performance affecting the login service. Customers can still log in, but the login process may take significantly longer than usual. Our team is actively investigating the cause and working to restore normal login performance. We apologize for the disruption and appreciate your patience. Your Sympa Team

Dear Customers, We have taken corrective action to address the degraded performance affecting the login service. According to our monitoring, the login service started operating normally at 10:25 EEST. Our team is continuing to monitor the service closely to confirm that performance remains stable. We apologize for the disruption and appreciate your patience. Your Sympa Team

Dear Customers, The login service has continued to operate normally, and our monitoring confirms that performance remains stable. We are therefore closing this incident. We apologize for the disruption and appreciate your patience. Your Sympa Team

**What happened** Between the evening of 30 August and mid-morning on 31 August, some customers experienced slower than normal login times. Logins completed, but response times were degraded during this period. **Why it happened** An internal configuration item was not renewed on schedule, which caused a background processing job to fall behind. Clearing the resulting backlog created a short load spike that extended the degraded performance before service returned to normal. **What we have done** Restored normal processing and cleared the backlog. Automated the renewal of this class of configuration so it no longer depends on a manual step. Added earlier alerting so the condition is detected before it reaches customers. Added pacing to backlog processing so recovery cannot itself degrade performance. **Timeline \(EEST\)** 30 Aug, evening: first signs of degraded background processing 31 Aug, 09:03: corrective change applied 31 Aug, 09:40: background processing resumes 31 Aug, 10:30: login performance back to normal

Dear Customers, We're experiencing an issue where the navigation structure does not show the page groups and pages as intended on employee profiles. We are currently investigating this and will provide an update by 10:30 EEST.

Dear Customers We've identified and resolved the issue causing the missing pages and groups. We will continue to monitor performance in order to minimise any setbacks. Thank you for your patience. Kind regards Sympa

Dear Customers, The issue affecting page groups has been fully resolved, monitoring is completed, and we have taken steps to prevent it from recurring. No customer action is required. We apologize for the disruption caused by this incident and thank you for your patience and understanding. Your Sympa Team

**What happened** * Page groups were not displayed on employee profiles **Why it happened** * An internal system that manages feature access reached its capacity limit, preventing page groups from loading **What we did** * We moved the page group configuration to use a more efficient system path, restoring the feature * We're implementing longer-term improvements to prevent this type of failure from recurring * We added automated tests to ensure this feature continues to work

Dear Customers, We have identified an issue affecting approvals on table rows on yesterday 2026-06-16 15:34 EEST and was fixed today 2026-06-17 08:18 EEST. Customers may have had issues to create approvals for affected table rows. Our team applied a fix to restore approval creation for the affected rows. Everything works as expected now. Out team is looking to fix the affected data. We will provide the next update when the affected data is fixed or latest by 12.00 EEST. To summarize everything works now. We apologize for the disruption and appreciate your patience. Your Sympa Team

Dear Customers, The fix done early in the morning for the issue affecting approvals on table rows remains in place, and approval creation is working as expected. Our team is continuing work on data fixing, to restore any missing approval records and to identify table rows that may require approval review as a result of changes made during the affected period. Customers may still see some approval records that have not yet been fully restored while this work is ongoing. We are actively progressing with the corrective actions and will provide the next update by 14:00 EEST, or sooner if there is significant progress. We apologize for the disruption and appreciate your patience. Your Sympa Team

Dear Customers, Approval creation for table rows continues to work as expected. Our team has prepared a corrective fix for the remaining affected data. Testing has started and is currently ongoing before the fix is applied. Customers may still see some approval records that have not yet been fully restored while this work continues. We will provide the next update by 16:00 EEST, or sooner if there is significant progress. We apologize for the disruption and appreciate your patience. Your Sympa Team

Dear Customers, Approval creation for table rows continues to work as expected. Our team has tested the corrective process in a non-production environment and is completing final adjustments before applying it to production. Once applied, the corrective process is expected to restore the missing approval records for the affected table rows. Customers may still see some approval records that have not yet been fully restored while this work continues. We will provide the next update by 19:00 EEST, or sooner if there is significant progress. We apologize for the disruption and appreciate your patience. Your Sympa Team

Dear Customers, Approval creation for table rows continues to work as expected. Our team has continued preparing the corrective process for the remaining affected approval data. Additional validation and adjustments are still required before the process can be safely applied to production. Customers may still see some approval records that have not yet been fully restored while this work continues. We will continue this work overnight and provide the next update by 09:00 EEST tomorrow, or sooner if there is significant progress. We apologize for the disruption and appreciate your patience. Your Sympa Team

Dear Customers, New approval creation for table rows continues to work as expected. Our team has continued working on the corrective process for restoring the remaining affected approval data from the earlier incident. Testing of the corrective process has not yet completed successfully, and additional adjustments are required before it can be safely applied. Customers may still see some approval records that have not yet been fully restored while this work continues. We will provide the next update by 12:00 EEST, or sooner if there is significant progress. We apologize for the disruption and appreciate your patience. Your Sympa Team

Dear Customers, Approval creation for table rows continues to work as expected. Testing of the corrective fix has now been completed in a non-production environment. Our team is preparing to apply the fix to the affected production data after office hours today. Customers may still see some approval records that have not yet been fully restored while this work continues. We will provide the next update after the production corrective action has been completed, or by 19:00 EEST. We apologize for the disruption and appreciate your patience. Your Sympa Team

Dear Customers, We are pleased to share that we have successfully implemented a fix for the majority of the rows affected during the incident, and these have now been returned to a pending approval state. We are currently working on resolving the remaining few cases. In addition, we continue to investigate and address the rows that were edited during the incident. These rows are currently in an approved state. We will provide our next update after the Midsummer holiday. Thank you for your patience and understanding and apologise for the inconvenience. Your Sympa Team

Dear Customers, The issue affecting approvals when creating and editing table rows was resolved on 2026-06-17 at 08:18 EEST, as communicated previously. Approval creation for table rows is working as expected, and the corrective fix has been applied.   The approval data for rows that were created during the incident have already been fixed 2026-06-18 by setting them to “pending approval” state. We are now completing the remaining data corrections for rows that were edited during the incident period. No customer action is currently required. We will contact affected customers directly if any follow-up actions are needed. We will provide the next update when the remaining corrections have been completed, or by 20:00 EEST.   We apologize for the disruption and appreciate your patience.   Your Sympa Team

Dear Customers, The data correction work has now been completed, and the affected rows have been returned to the “pending approval” state. This statuspage topic can now be closed as fully resolved. No customer action is required. As communicated previously, the underlying issue was resolved on 2026-06-17 at 08:18 EEST, and approval creation for table rows has been working as expected since then. We apologize for the disruption caused by this incident and thank you for your patience and understanding while we completed the corrective work. Your Sympa Team

**What happened** Between **16 June 2026 at 14:00 EEST** and **17 June 2026 at 08:30 EEST**, an issue affected approval workflows in table-based forms. During this period: * New rows created in tables with approval fields were saved successfully, but the approval controls were not displayed, preventing users from approving or declining the rows. * Editing existing rows did not correctly reset approval status when required. Previously approved or declined rows retained their existing status instead of returning to a pending state. * Users were unable to complete approval actions for affected rows. After the issue was resolved, we repaired all affected records. Rows created during the incident were restored on **18 June**, and rows updated during the incident were restored on **22 June**. **Why it happened** The incident was caused by an operational error during preparation for a planned release, resulting in an unintended change that affected approval workflows. **What we did** Once the issue was identified, we immediately assembled an incident response team to investigate and resolve the issue. We removed the unintended change, developed dedicated repair tools to restore the affected approval records, and successfully completed repairs for all known impacted data. To help prevent similar incidents, we are strengthening our release processes and enhancing our monitoring and alerting capabilities to detect and respond to similar issues more quickly.

Dear Customer, We are currently investigating an issue affecting integrations. Customers may experience failed or delayed integration processing. Our team is actively investigating the root cause and working to restore normal integration processing. We will provide the next update by 13:00 EEST, or sooner if there is significant progress. We apologize for the disruption and appreciate your patience. Your Sympa Team

Dear Customer, We have identified the cause of the issue affecting integrations. Customers may still experience delayed integration processing. Our team is continuing mitigation work and manually reprocessing affected files where possible while we work to restore normal processing. We will provide the next update by 15:00 EEST, or sooner if there is significant progress. Your Sympa Team

Dear Customer, We are continuing work to restore normal integration processing. Customers may still experience delayed integration processing. Our team is preparing a fix and testing it before applying it. We are also continuing mitigation work and manually reprocessing affected files where possible. We will provide the next update by 16:30 EEST, or sooner if there is significant progress. Your Sympa Team

Dear Customer, We have applied fixes for the issue affecting integrations and are monitoring their effect. Integration processing has improved, but some data from last night still requires manual handling. Our team is continuing this work and will monitor the results of the fixes throughout the night. We will keep this incident open and provide the next update by 19:00 EEST, or sooner if there is significant progress. Your Sympa Team

Dear Customer, We have applied mitigation actions for the issue affecting integrations and are continuing to monitor integration processing. Our team is monitoring the evening and overnight processing runs to confirm stability. We are also continuing manual handling of any remaining affected data where needed. We will keep this incident open while monitoring continues and will provide the next update by 09:00 EEST tomorrow, or sooner if there is significant progress. Your Sympa Team

The mitigation actions taken yesterday has fixed the issue. The performance has also improved significantly. We did not detected such issues in integrations during yesterday evening, during the night nor during the morning. We confirm everything is operational and close this ticket. Post-mortem will be released later on.

## Post mortem for customers ### What happened Some integrations were delayed or failed during the nightly processing window because Azure Blob Storage operations were slower than usual. The integrations performed more Azure Blob listing/checking operations than expected. The number of `ListBlobs` calls was around double compared to normal days. This affected to one integration application. ### Why it happened Most probably, Azure Blob Soft Delete or increased blob volume caused slower listing operations during the night. This affected integrations that rely on file lookup logic to Azure Blob. ### What we did We optimized Azure Blob existence checks and flows in the integration application that got affected. As a result, the number of `ListBlobs` calls decreased by around 20%, and the next nightly integration runs completed normally, with better performance. The same fix was also applied to other integration applications.