[Minor] Issues with Uploads

Final update

We recently addressed issues affecting file uploads and edits that create new file versions. We want to explain what happened and what we have done to prevent it from happening again. Between Jul 26, 2026 4:38 PM PDT and Jul 28, 2026 10:34 AM PDT, some users may have experienced delays or failures when uploading files or saving edits that create new file versions. The impact was limited to cases with a high number of concurrent uploads or edits on the same file. During this period, concurrent upload and edit traffic contended on shared database locks while creating new file versions. Under load, an overly conservative insert locking strategy acquired locks, creating a bottleneck in the database. The contention was amplified by background processes that post-process the uploaded file and attach additional information to every new version, competing for the same locks. # Analysis This incident highlighted several opportunities for improvement: * Lock-wait failures do not appear in our usual change-stream / mutation telemetry, which delayed our investigation. * Background processes can contend with upload and edit paths that create new versions. Our development environments did not

1. Postmortem · Aug 4, 04:09 UTC
   We recently addressed issues affecting file uploads and edits that create new file versions. We want to explain what happened and what we have done to prevent it from happening again. Between Jul 26, 2026 4:38 PM PDT and Jul 28, 2026 10:34 AM PDT, some users may have experienced delays or failures when uploading files or saving edits that create new file versions. The impact was limited to cases with a high number of concurrent uploads or edits on the same file. During this period, concurrent upload and edit traffic contended on shared database locks while creating new file versions. Under load, an overly conservative insert locking strategy acquired locks, creating a bottleneck in the database. The contention was amplified by background processes that post-process the uploaded file and attach additional information to every new version, competing for the same locks. # Analysis This incident highlighted several opportunities for improvement: * Lock-wait failures do not appear in our usual change-stream / mutation telemetry, which delayed our investigation. * Background processes can contend with upload and edit paths that create new versions. Our development environments did not fully test this particular interaction under load. Remediation combined an immediate reduction in non-essential background scan load with a code change that relaxed the overly conservative locking behavior, while preserving the intended isolation guarantees. # Corrective Actions Box has initiated th
2. Resolved · Jul 28, 04:57 UTC
   After further monitoring, this incident is now considered resolved. Box services have been restored to full functionality. Please contact Box Support at https://support.box.com/ if you continue to experience any issues.
3. Monitoring · Jul 28, 04:22 UTC
   Our team has taken steps to remediate this issue and is seeing improvements. We are continuing to monitor for any additional impact.
4. Identified · Jul 28, 04:02 UTC
   We are continuing to work on a fix for this issue.
5. Identified · Jul 28, 03:08 UTC
   Our team has identified the underlying cause of this issue and is working to take remediating steps. We will provide additional updates as they become available.
6. Investigating · Jul 28, 02:58 UTC
   We are investigating an ongoing issue affecting uploads. We will provide more information as soon as it is available.