Sympa HR experienced a minor incident on April 24, 2026 affecting System availability, lasting 3h 53m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Apr 24, 2026, 08:26 AM UTC
We have identified an issue in Sympa that may have impacted some customers. Users may experience errors when attempting to save certain data. We are working to resolve the problem and will provide an update when it is confirmed to be fully resolved.
- monitoring Apr 24, 2026, 08:55 AM UTC
We have identified the root cause of the issue and are currently applying a fix. The update is being rolled out, and we expect the issue to be resolved shortly. Our team is closely monitoring the situation to ensure everything returns to normal for affected customers. Your Sympa Team
- resolved Apr 24, 2026, 12:19 PM UTC
The issue has now been resolved, and our services are operating normally. We have completed monitoring and can confirm that the fix is working as expected. Thank you for your patience. Your Sympa Team
- postmortem May 04, 2026, 07:50 PM UTC
**Customer impact** Some customers experienced errors when attempting to save data in Sympa. This resulted in failed updates with the 5003 error given on the screen while attempting to save the data in the form. **Timeline \(UTC\)** * **April 23, 18:00 UTC** — A configuration change was deployed to production as part of a planned feature rollout. * **April 24, 06:30 UTC** — The issue was detected after customer reports of save errors \(error code 5003\). * **April 24, 08:48 UTC** — The issue was fully mitigated by reverting the configuration change. Total time from detection to resolution: **2 hours 18 minutes**. **What happened** The issue was caused by a recently enabled feature related to how certain changes are processed in the system. This change unintentionally affected normal save operations for some users. **Resolution** We identified the problematic feature configuration, verified the fix in our test environment, and then disabled it in production, which resolved the problem. Normal functionality has been fully restored. **Next steps** * Root cause analysis is underway to determine why this configuration caused permission-related errors. * We will strengthen our pre-deployment validation to catch similar issues before they reach production.