The fix is confirmed working and MakoFlow job execution has fully returned to normal.

Root cause: We observed a spike in duplicate EDIFACT APERAK files being sent by specific external market partners. This unexpected volume of duplicates triggered the concurrency issue that led to delayed job processing.

While the duplicate files originate outside our systems and are outside our direct control, we've improved how MakoFlow handles this scenario so that similar spikes will no longer impact job execution.

AS4 connections and the API were not affected at any point during this incident.

Thank you for your patience while we resolved this.

We've identified the root cause of the concurrency issue affecting MakoFlow job execution and have applied a fix. Job processing is returning to normal, and we're closely monitoring the system to confirm full stability.

AS4 connections and the API remain unaffected.

We'll provide a final update once we're confident the issue is fully resolved.

We're aware that MakoFlow job execution is currently delayed for some jobs due to a concurrency issue affecting specific scenarios. Our team is actively investigating and working on a fix.

AS4 connections and the API are not affected and continue to operate normally.

We'll post updates here as we learn more.

The identified load balancer misconfiguration has been resolved. All backend services are now fully operational.

We're reviewing our deployment and monitoring processes of this infrastructure component to help prevent similar issues going forward.

Please reach out to helpdesk@support.mako365.com
for any questions or if you continue to experience issues.

Thank you for your patience.

We are observing recovery and keep monitoring.

We have identified the erroneous configuration change and are attempting a rollback.

We are currently experiencing an issue affecting backend services across MakoFlow Our team has identified the root cause as a problem with our database load balancer and is actively working on a resolution.

Impact: All backend services are currently down. Users may be unable to access core functionality.

This incident has been resolved. The load balancer connectivity issue between the application and the database has been fixed, and backend services are fully operational again.

We will conduct a thorough investigation into the root cause of this incident and put measures in place to prevent it from happening again.

We apologize for any inconvenience this may have caused and thank you for your patience.

As part of our efforts to resolve the ongoing backend connectivity issue, we are switching back to the previous primary database. This action is being taken to restore stable communication between the application and the database via the load balancer. Users may experience a brief interruption during the switch.

We will update this page once the failover is complete and services are confirmed stable.

We're currently investigating an issue causing our backend service to be unreachable. Users may experience failed requests or timeouts across the app. Our team has identified the issue as a communication failure between the application and the database via the load balancer, and we're working on a fix. We'll share an update as soon as we have more information.