[Medium] Issues with File Requests

What to do

• Check whether you use Box Sharing (Shared Links). Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 56m it lasted.

  Anything that failed between 2026-07-23 09:45 UTC and 2026-07-23 11:42 UTC may need a replay.

• Subscribe to Box's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=box works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Box 4

1. investigatingJul 23, 2026, 9:45 AM UTC

   We are investigating an ongoing issue affecting metadata updates using File Request. We will provide more information as soon as it is available. Users of this service may face delays in metadata updates while attempting to upload files using File Request.

   provider

2. identifiedJul 23, 2026, 11:05 AM UTC

   The underlying cause of the issue has been identified and efforts are underway to restore stability. Box continues remediation efforts to fully restore the metadata functionality of File Requests.

   provider

3. resolvedJul 23, 2026, 11:42 AM 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.

   provider

4. postmortemAug 5, 2026, 2:03 AM UTC

   We recently addressed an issue affecting metadata updates using File Request in Box. We would like to take the opportunity to further explain the issue and the steps we have taken to keep similar issues from happening in the future. Between 09:10 AM PDT on July 22, 2026 and 03:36 PM PDT on July 23, 2026, some users may have experienced delays in metadata updates while uploading files using File Request. The issue occurred when repeated attempts to process a subset of unsuccessful metadata events reduced available processing capacity and delayed other events. We restored the metadata functionality of File Requests by limiting unnecessary retries, reducing processing idle time, and improving the handling of failures that would not succeed when retried. In addition, we are improving retry behavior, monitoring, and response procedures for similar asynchronous processes. # Analysis At the time of the issue, the system automatically retried failed file processing. During an extended period of failures, these retries consumed most of the system's capacity, causing files to pile up in a queue. As processing slowed, more files encountered issues that retries could not resolve, further increasing the delay. We restored normal processing by temporarily reducing retry attempts, removing redundant retries, and allowing permanent failures to fail without being repeatedly processed. We continued monitoring the service before confirming that full functionality had been restored. # Corrective Actions The following corrective actions have been completed or are planned: * Completed changes to limit retries and stop repeatedly processing failures that cannot be resolved through retries. * Applying the same, improved retry handling to other asynchronous processes, preventing similar occurrences from happening to other File Request features. * Improving alerting and response procedures for processing backlogs and retained unsuccessful events to ensure that temporary issues can later be retried safely. We are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter. Sincerely, The Box Team

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.