Factorial HR incident

Time Tracking service outage

Resolved after 12 hours, on May 19, 2020.

postmortem May 19, 2020, 03:21 PM UTC

# What happened? Today we made an upgrade in the Time Tracking service that involves a migration of the settings of each company to the new implementation. This process took longer than expected disabling the service up to 1 hour in some companies # How are we going to prevent similar issues in the future? When an upgrade like this requires big Data migrations, procure to implement it backward compatible \(if possible\) and in low-impact times \(nights/weekends\)

Started
May 19, 2020, 01:30 AM UTC
Resolved
May 19, 2020, 01:30 PM UTC
Duration
12h
Detected by Pingoru
May 19, 2020, 01:30 AM UTC

Update timeline

  1. resolved May 19, 2020, 03:16 PM UTC

    The Time Tracking service was disabled for some companies, preventing employees to clock-in and out, in desktop and mobile App

  2. postmortem May 19, 2020, 03:21 PM UTC

    # What happened? Today we made an upgrade in the Time Tracking service that involves a migration of the settings of each company to the new implementation. This process took longer than expected disabling the service up to 1 hour in some companies # How are we going to prevent similar issues in the future? When an upgrade like this requires big Data migrations, procure to implement it backward compatible \(if possible\) and in low-impact times \(nights/weekends\)

Your product runs on more than Factorial HR

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →