Major incident
HiBob: We’ve identified an issue with employee profile work tables
Aug 31, 2026, 11:33 UTC
started
15:59 UTC
resolved
4 h 25 min
duration
Affected: Employee Profile and Fields
Current status of HiBob: Operational — live HiBob status
Timeline
- Aug 31, 2026, 11:33 UTCinvestigatingWe confirm there is a problem with the employee profile work tables, and we’re working to resolve it.
- Aug 31, 2026, 12:55 UTCidentifiedWe have identified an issue where users may encounter errors when adding or updating rows in history tables within the employee profile. Our team has found the root cause and is working to resolve the issue.
- Aug 31, 2026, 15:24 UTCmonitoringWe have deployed a fix for the issue affecting employee profiles updates and are monitoring the results to confirm the issue is fully resolved.
- Aug 31, 2026, 15:59 UTCresolvedThe issue has been resolved. A regression caused validation to run across all history table entries, including historical rows containing archived values, which caused updates to fail. We have updated the validation to apply only to rows that have been changed.
Updates as published by HiBob (original).
Other services with incidents at the same time
- OneIT 12:23 UTC · CAS Authentication Issues
- Asaas 11:59 UTC · Indisponibilidade na geração de QRCodes Dinâmicos / Pix
- Qualtrics 11:51 UTC · Salesforce Workflow Connection issues in all Regions
- AppState 11:23 UTC · WebFocus authentication issues
- BrowserStack 11:07 UTC · Automate is facing issues
- BrowserStack 11:07 UTC · App Automate is facing issues
More HiBob incidents
- October 19, 2026 We’ve identified an issue with our Career site service
- October 14, 2026 We’ve identified an issue with our Compensation service
- August 26, 2026 Talent service - Performance and Surveys aren't loading
- August 4, 2026 Workforce Planning - Can't load existing position
- June 15, 2026 We’ve identified an issue with our Hiring module.
- April 7, 2026 Some users may experience slower-than-usual performance at the moment. Our team is aware of the issue and is actively working to identify the root cause and resolve it. We appreciate your patience and will share updates as we make progress.