Orchestry Outage History

We’re aware of an issue causing File Archival jobs to fail for some customers in our US region. Affected jobs fail during execution, and archival actions scheduled during this period may not have completed. We’ve traced the cause to a recent change in Microsoft SharePoint Online that affects how certain search requests are processed. Microsoft has acknowledged reports of the problem, which appears to be impacting a subset of SharePoint Online tenants. Our team is investigating if the issue can be worked around on our side so that File Archival no longer depends on the affected behavior, and we’re also monitoring Microsoft’s progress on a resolution. No files have been lost or modified as a result of this issue; jobs that failed simply did not run. We’ll post another update as soon as we have more information or a fix is deployed.

We are experiencing delays in background processing across all regions. Some customers may see workspace provisioning and reporting data updates take longer than usual or appear stuck in progress. The Orchestry app itself remains available. We have identified the cause and are working on remediation. No data has been lost, delayed work will complete once processing recovers.