We are experiencing delays in schedules that rely on flows to complete. We are also seeing delayed updates to the UI from flows finishing.

Root cause is related to a Vista service pack that released overnight to customers. We have identified the issue, but a queue remains. We have scaled up to process that queue more quickly.

We expect delayed updates for a few more hours.

We have been working through our backlog as fast as we can. There was a very large backlog so it took some time. Flows are still running but we have a backlog for the next 15-minutes. We continue to monitor.

Queue has returned to normal ranges. All schedules and flows are completing in expected timeframes. This incident has been resolved.

We are experiencing delays in schedules that rely on flows to complete. We are also seeing delayed updates to the UI from flows finishing.

We have identified the issue, but a queue remains. We have scaled up to process that queue more quickly. We expect delayed updates for about another hour.

Queue has returned to normal ranges. All schedules and flows are completing in expected timeframes. This incident has been resolved.

We are experiencing an issue with our Partner Portal (http://partnerapp.xchange.trimble.com). This website is used by two partners, Procore and Newforma. The website is offline at the moment and we are looking into it.

• Procore is unable to review configurations in the Partner Portal.
• Newforma customers are unable to view or modify project mappings.

We are actively working on the issue and will provide status updates as we have them.

NOTE: No other integrations or services are impacted.

We have identified and fixed the issue with Partner Portal. The site is working since 12:15pm CST.

This was an issue in the UI for that site. All other services were working normally across the platform.

We are currently investigating an issue impacting all workflow based integrations. We know the root cause and are working to resolve the issues. Cache writing is not completing as expected, which leads to flows not triggering from the cached data events. We will provide updates as we have them.

We have identified and addressed the issue with cache writing. Service disruption started at 12:03pm CST and lasted until 1:11pm CST.

During this window, cache writing would have failed and flows would not trigger automatically.

The next scheduled cache write will work normally, cache write the data, and then trigger the associated flow.

We will continue to monitor the platform.

This incident has been resolved.

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.