Database
We are experiencing a service disruption that is impacting the Procore <> Vista integration for legacy customers. All other integrations working fine and the Procore V2 integration is working fine.
We are actively investigating the issue, which started happening at noon CST today.
We have identified the issue and deployed a hotfix. Procore <> Vista integration services are running again.
- Syncs from Vista will complete on next hourly run; customers would have experienced a delay in data showing for import.
- Exports to Vista were reaching Vista successfully but not closing out. The next hourly sync will complete and mark them synced in Procore where needed.
We will continue to monitor for a while longer.
Procore <> Vista integration services are completing normally since 3pm CST. This incident has been resolved.
We are investigating an issue with job logs being delayed. Services and workflows are running normally, but we are seeing delayed job logs displaying in App Xchange.
We have identified the issue and are back to normal since 2:40pm CST (20-mins ago). We will continue to monitor for a while longer.
There was a delay in job logs starting 1:30pm CST and lasting to 2:40pm CST. Services and workflows ran normally, and this would have been limited to job logs displaying in App Xchange.
Job logs would have been delayed during this timeframe.
The team moved quickly to remediate, and this incident is resolved.
There was a minor delay in job logs starting 8am CST and lasting to 9:47am CST. Services and workflows ran normally and this would have been limited to job logs displaying in App Xchange.
Job logs would have been delayed during this timeframe.
The team moved quickly to remediate, and this incident is resolved
We have been alerted to elevated API response times which is resulting in increased page load times in the App Xchange UI.
Response times have improved, but we are still seeing some slowness. We are continuing to investigate the issue and will provide another update shortly.
Our team has determined that the previously reported issue is now fully resolved. Thank you for your patience during this incident.
To ensure the continued performance and dependability of our platform, we have a planned maintenance window that will take place on:
Date: 2025-07-30 (Wed.)
Time: 7:00 PM - 11:00 PM CDT
During this period, App Xchange will be completely unavailable. We have intentionally planned for this work to take place during a period of historically low usage to minimize impact. Upon completion of this work, any jobs or workflows that were interrupted or delayed will be prioritized and executed to bring data states back to normal.
This maintenance will allow us to enhance our underlying infrastructure. We are confident these upgrades will provide a more flexible and dependable experience in the long term.
If you have any questions, please don't hesitate to contact us at xchange_support@trimble.com.
Thank you,
The Trimble App Xchange Team
Schedule maintenance is complete. We are closing this planned maintenance window.
We are investigating an incident related to our database. Services may be impacted and we are looking into it.
We have identified the issue and are performing maintenance to remediate the issue. This is impacting services. We will provide updates as we have them.
We completed some maintenance and the platform is operational. Services are running and we continue to monitor.
Some additional maintenance was completed on our database a few hours ago. We have been operational since the afternoon, but wanted to continue monitoring. We consider this incident 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.
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 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