Candidates Scheduled with Unavailable Interviewers

Update timeline

1. resolved Mar 30, 2026, 09:15 PM UTC

   Candidates may have scheduled with unavailable interviewers during the following time periods: * Mar 24, 8:21AM - 9:52AM PDT * Mar 25, 9:52AM - Mar 27, 5:34AM PDT At the scheduled time, the interviewer may already have had a meeting. This happened because we shipped a bug that incorrectly calculated or displayed the interviewer’s availability. This bug affected the following scheduling features: * Manual scheduling * Direct booking links * Advanced scheduling We will be posting a post-mortem about how this happened and what we’re doing to prevent this issue in the future.

2. postmortem May 06, 2026, 10:09 AM UTC

   ### **Summary** For a brief period on Monday, March 24, and from Tuesday, March 25 to Thursday, March 27, 2026, Ashby's scheduling features displayed incorrect interviewer availability for a subset of organizations with the Google Workspace integration. This allowed candidates to be scheduled even when an interviewer may already have a meeting. This bug affected the following scheduling features: * Manual scheduling * Direct booking links * Advanced scheduling The issue only impacted organizations using Google Calendar sync without domain-wide delegation. ### **Why did this happen?** Ashby integrates with Google Calendar to display interviewer availability and power our scheduling features. Because some interviewers aren’t authenticated Ashby users, we occasionally read their calendar data on behalf of a user who is. A code change deployed on March 24 updated the calendar synchronization logic as part of an improvement to our Google Calendar authorization process. A bug in this logic incorrectly conflated the interviewer’s calendar with the authenticated user's, resulting in inaccurate availability being displayed during scheduling. The code change was initially deployed on March 24, then briefly reverted, and redeployed on March 25, which is why there were separate windows of impact. ### **How did we resolve the situation?** The bug was active during three separate windows: * Monday, March 24, 8:21 AM - 9:52 AM PDT \(approximately 1.5 hours\) * Tuesday, March 25, 7:05 AM - 7:52 AM PDT \(approximately 47 minutes\) * Tuesday, March 25, 9:52 AM - Thursday, March 27, 5:34 AM PDT \(approximately 44 hours\) On Thursday, March 27, 2026, at 4:31 AM PDT, a customer reported that an interviewer’s availability appeared incorrect. At 5:10 AM PDT, we identified the root cause, and at 5:34 AM PDT, we deployed a fix and triggered calendar resyncs for affected organizations to restore accurate availability data. ### **What have we put in place to prevent it from happening in the future?** 1. **Improved static analysis checks.** We improved static analysis checks to ensure similar code changes are analyzed for correctness before they reach production. 2. **Improved testing for calendar authorization scenarios.** The bug affected a specific authorization configuration that is difficult to replicate in our test environments. We are building improved test tooling to enable automated tests across even more permutations of integration configurations. 3. **Better monitoring for calendar sync accuracy.** We are adding monitoring that will alert us when calendar data retrieved through this particular authorization path does not match the intended user.