Delayed syncs & Mapping saving error

Update timeline

1. investigating Mar 23, 2026, 08:21 AM UTC

   If you are experiencing Exact Online issues, please let an admin user re-authenticate this connection. If you are noticing mapping issues, we are currently still investigating the issue.

2. investigating Mar 23, 2026, 08:38 AM UTC

   We are currently investigating an issue affecting the sync performance and application speed. We are actively working on a resolution. Updates will be communicated as soon as they are available.

3. monitoring Mar 23, 2026, 09:24 AM UTC

   To alleviate platform-wide slowdowns caused by high data volume, we have implemented batch processing to manage the workload more efficiently. While the general platform looks stable now, please note that some synchronizations may experience temporary delays as we process the remaining queue.

4. monitoring Mar 23, 2026, 12:03 PM UTC

   We notice the platform is still experiencing a general delay impacting syncs, mapping, and manual uploads. We are processing the remaining as quickly as possible. Our apologies for the inconveniences!

5. monitoring Mar 24, 2026, 08:03 AM UTC

   We continue to experience syncing delays due to the large volume of data being processed. We are actively working to mitigate this issue and will provide regular updates throughout the day.

6. monitoring Mar 24, 2026, 10:35 AM UTC

   Our technical team is currently taking action to resolve the ongoing sync issues. Our next steps will be: All current syncs will be cancelled so that the sync queues are reset. This should unblock affected client files so you can continue working again. After that, if you are (still) seeing an error message in a file, you will be able to restart the sync for that specific client file by clicking the sync button at the top of the file page. New syncs may run a bit slower at first, but they are expected to complete successfully. We are treating this issue with the highest priority and will continue to monitor the situation closely. The next update will be provided at 13:00 CET.

7. monitoring Mar 24, 2026, 12:00 PM UTC

   We have implemented a solution and are actively monitoring the situation. You may experience minor delays until your sync begins and is processed, as we are working through a significant backlog. The next update is scheduled for 3 PM CET.

8. monitoring Mar 24, 2026, 02:00 PM UTC

   The solution we implemented is stable, and we continue to monitor the situation with priority. Minor sync delays may still occur. The next update is scheduled for 5 PM CET.

9. monitoring Mar 24, 2026, 04:00 PM UTC

   The solution we implemented is still running stably, and we will continue monitoring the backlog overnight. If you still encounter an error in your file, you can always trigger the sync manually (at the top of the page), but minor delays may still occur. The next update is scheduled for Wednesday, 25/3 at 9:00 CET.

10. monitoring Mar 24, 2026, 04:09 PM UTC

    The solution we implemented is still running stably, and we will continue monitoring the backlog overnight. If you still encounter an error in your file, you can always trigger the sync manually (at the top of the page), but minor delays may still occur. The next update is scheduled for Wednesday, 25/3 at 9:00 CET.

11. monitoring Mar 25, 2026, 08:00 AM UTC

    Our nightly sync completed successfully, and file syncing is now behaving normally. We will continue to monitor the situation, and the next update is expected at 12 PM. If you notice anything out of the ordinary, please contact support.

12. monitoring Mar 25, 2026, 08:02 AM UTC

    Our nightly sync completed successfully, and file syncing is now behaving normally. We will continue to monitor the situation, and the next update is expected at 12 PM. If you notice anything out of the ordinary, please contact support.

13. resolved Mar 25, 2026, 11:02 AM UTC

    Following the implemented solution, sync behavior has returned to normal, and mapping issues have been restored. Please address any future sync-related issues to the support team. This incident will now be closed.