June 5, 2024

Release notes

New feature

We've added color coded status indicators and enhanced error messaging for partially successful events to the Reporting pages in the SaaS Protection application. This update provides clearer and more detailed information regarding backup, restore, and export events and helps you better understand backup errors and event statuses.

The information surfaced is as follows:

  • Status indicators:

    • Yellow: Partially successful events

    • Green: Successful events

    • Red: Failed events

    • Grey: Check was performed for differences; no new files were detected; new snapshot was created; no backup occurred

  • Enhanced error messaging:

    • Each failed item now includes the following details:

      • Item name

      • Item type

      • Error type

      • Error message

    • If an error invalidates the whole event, a single error message will appear, preventing the process from proceeding with individual files.

    • If each file encounters a separate error, and all files fail, SaaS Protection will flag the record with a yellow indicator.

    • If some files succeeded but other files failed, SaaS Protection will flag the record with a yellow indicator and a drop-down menu enumerating the failed items.

Improvement

  • We've enhanced export performance for large datasets. You'll notice a significant speed improvement when performing a CSV export for 1,000 or more seats.

Bug fixes

  • We've fixed an issue that caused OneDrive backups to be restored without their sharing permissions.

  • Under certain circumstances, SharePoint backups could fail in a "404 Http Not Found Error" state. We've corrected this issue.

  • This release corrects a scenario in which Google Workplace Mail backups failed due to invalid startHistoryId requests, causing 404 errors and potential rate-limiting (429 or 503 errors). Backups now complete successfully, and non-existent users or items are correctly archived.

  • We've improved SharePoint recovery logic, ensuring files are correctly marked as restored in the UI and 404 errors no longer occur, regardless of versioning settings.