Sympa HR experienced a minor incident on May 8, 2026 affecting Integrations, lasting 6h 15m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 08, 2026, 12:55 PM UTC
Dear Customer, We are investigating an issue that affected some ongoing integrations. We have identified cases where integrations using the POST action to create new users were affected. The root cause has already been fixed and the correction has been deployed to production. Our team is now identifying affected users with missing Employee IDs and is working to correct the impacted data. We will continue to monitor the situation closely and provide further updates as needed. Your Sympa Team
- monitoring May 08, 2026, 03:16 PM UTC
Dear Customer, The implemented fix is working as expected, and we have moved this incident to monitoring. Integrations using the POST action to create new users are now operating normally in production. Our team is continuing to review previously affected cases, including users with missing Employee IDs, and is working to correct any impacted data where needed. We will continue to monitor the situation closely and provide further updates if needed. Your Sympa Team
- resolved May 08, 2026, 07:11 PM UTC
Dear Customer, This incident has now been resolved. The fix has been deployed to production, and integrations using the POST action to create new users are operating normally. Our team has reviewed the affected cases related to missing Employee IDs and completed the required corrective actions. We will continue to follow up internally to ensure everything remains stable. Your Sympa Team
- postmortem Jun 05, 2026, 03:06 PM UTC
**What happened** Between 28 April and 8 May 2026, employees created through our API integration could be left without an automatically generated identifier number. The employees themselves were created successfully, but the identifier field remained empty, which may have affected downstream integrations that rely on this data. **Why this happened** A defect in our integration API caused the automatic identifier assignment to be skipped in a specific configuration scenario. **What we did** The issue was detected on 8 May 2026, and a fix was deployed the same day. Identifier numbers are now always assigned correctly when employees are created through the API. **How we are preventing recurrence** Additional automated test coverage has been implemented for this scenario. The affected functionality is now validated through code-level tests during development, and end-to-end system tests are being expanded to verify the behavior before future releases are deployed.