Dear Customer,

Our team is investigating an issue on the following service(s):

App Xchange Platform

We have identified and address the root cause already, this is a retroactive notification.

During the outage App Network and Direct API, specific flow steps and service runs are encountering failures.

We sincerely apologize for the service interruption and will provide further updates as soon as possible.

The team has resolved the primary issue and is monitoring the situation.

10:15 am to 22:15pm GMT

We are experiencing processing delays in schedules that is resulting in some activity to be delayed by as much as 10 minutes. We are actively working to address the issue.

We expanded capacity today to address the issues with schedules not starting on time. Queues are returning to normal, metrics are back to regular thresholds, and things are trending in the right direction since 10:51am CST.

Schedule delay is down to 5-mins or less.

We continue to monitor the platform.

Schedules are back to normal since 11:33am CST. Processing is now within expected time ranges and this incident is resolved.

We have identified an issue impacting Concur or FTP-based integrations. The sync between Concur List and some FTP connections are failing at a higher rate than normal. We are taking steps to mitigate and will deploy a hotfix as soon as possible.

We will post a status update when services for those affected integrations has returned to normal. We expect this to be later today.

Hotfix was released and services have returned to normal. The next scheduled Concur List refresh or FTP transfer will work as expected.

This incident is resolved.

We are currently investigating an issue impacting all workflow based integrations. We do not yet know the root cause, but early indications point to an Azure issue. We will provide updates as we have them.

We have confirmed this is an Azure incident in the South Central region. We are attempting to gather additional information to determine a path to restore services.

The underlying Azure issue seems to have been resolved and workflows are now executing, albeit delayed. We are actively monitoring the situation to ensure we return to full health.

The platform is healthy and we will continue to monitor.

We are experiencing processing delays related to connector actions that are resulting in some activity to be delayed by as much as 50 minutes. We are actively working to identify and address the root cause.

Processing is now within expected time ranges.

We are investigating an issue causing delays in the processing of workflows. We will post an update as we have them.

We've identified the issue and took steps to mitigate. We are monitoring to ensure the platform is working through the backlog. We will post updates as services return back to normal.

We are working down the queue, currently expect to return to normal later tonight. We are continuing to monitor for any further issues, but will leave this incident open and review in the morning.

Things operated normally overnight. This incident has been resolved.

Earlier today we identified an issue causing exports from Procore to fail at a higher than normal rate. This is limited to the Procore Vista legacy integration.

Customers would have seen an error message "Failed to update. Please try again later." The customer could have tried again and gotten success. However, the error rates were unacceptable and so we took action.

The issue has been fixed as of 3pm CST 9/18.

If a customer has a failed export, have them try again. The data is not stuck or queued and it is safe to simply try export again.

The incident has been resolved.

We are experiencing elevated error levels since about 11am CST that is impacting legacy services and causing performance delays. We are actively investigating the issue.

We have identified the issue and determined that it is limited to the Procore <> Vista legacy integration.

This incident is now limited to the Procore <> Vista legacy integration.

The Viewpoint services for the Procore <> Vista integration are failing to complete at a higher than normal rate. It is not all customers and it is not every hourly run, but the failure rate is higher than normal. Customers would experience a delay in data transfer to Procore and a higher than normal failure rate when exporting (the error may say something generic like failed entirely).

We expect some database maintenance to complete overnight. We will continue to monitor the situation. We plan to leave this incident open and provide an update in the morning.

Maintenance completed around 6:51pm late yesterday. Legacy Viewpoint syncs for the Procore <> Vista integration started working normally after that. They ran overnight and through this morning as expected.

This incident has been resolved.

There is an issue preventing processing of workflows. We have identified and addressed the issue. We are continuing to monitor, but need to work through the queue. We will post an update as soon as we have more info.

Monitoring We are working down the queue, currently expect to return to normal in 1-2 hours. We are continuing to monitor for any further issues.

This incident has been resolved.

We have identified the issue and the impact is minimal to end customers, but not resolved to our high standards. We are keeping this incident open to review in the morning. Since 5:17am CST 6/25 there have been an abnormal number of schedules that finish a service, but remain in a started status. It will then appear as "Cancelled" in the job logs after a period of time. We will continue to monitor, and provide updates tomorrow morning as we have them.