FloQast incident

Audit Log Event Capture

Resolved on December 19, 2025.

postmortem Mar 30, 2026, 09:16 PM UTC

**Summary:** Certain audit log events were not visible within the platform during the impacted period. **Root Cause:** A code change intended to reduce duplicate backend log entries introduced a gap in event capture due to an unaddressed dependency in the release process. As a result, some audit log events were not properly recorded or displayed. **Immediate Resolution:**The code change was reverted to restore audit log functionality. Engineering identified the affected time window, recovered available audit log data, and restored visibility of impacted events. **Follow-up Actions:** The team reviewed and reinforced software development lifecycle \(SDLC\) processes, including validation of dependencies during testing and deployment. Additional controls have been implemented to ensure completeness and reliability of audit log capture going forward.

Started
Dec 19, 2025, 10:15 PM UTC
Resolved
Dec 19, 2025, 10:15 PM UTC
Duration
–
Detected by Pingoru
Dec 19, 2025, 10:15 PM UTC

Update timeline

  1. resolved Dec 19, 2025, 10:15 PM UTC

    Dec 19, 14:15 PST Resolved - Certain audit log events are not appearing within the audit log export during an impacted period.

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

    Certain audit log events are not appearing within the audit log export during an impacted period.

  3. postmortem Mar 30, 2026, 09:16 PM UTC

    **Summary:** Certain audit log events were not visible within the platform during the impacted period. **Root Cause:** A code change intended to reduce duplicate backend log entries introduced a gap in event capture due to an unaddressed dependency in the release process. As a result, some audit log events were not properly recorded or displayed. **Immediate Resolution:**The code change was reverted to restore audit log functionality. Engineering identified the affected time window, recovered available audit log data, and restored visibility of impacted events. **Follow-up Actions:** The team reviewed and reinforced software development lifecycle \(SDLC\) processes, including validation of dependencies during testing and deployment. Additional controls have been implemented to ensure completeness and reliability of audit log capture going forward.

Your product runs on more than FloQast

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 →