Incident has been resolved.

A fix to ignore 3rd party failures of components unused in our stack has been deployed. We're monitoring the status

The problem has re-appeared after the 3rd party system re-reported issues with one of its systems.

Live status monitoring confirm the situation is resolved and calls can come through again.

Partial degradation - The issue seems resolved. We're monitoring the status of the system.

The issue is linked to authentication with a third-party provider. We are rotating the credentials now and will share a further update shortly.

We are currently investigating an issue affecting our call platform. Incoming calls are failing or being dropped, and customers may be unable to connect. Our engineering team is actively investigating and we will share an update as soon as we know more.

Traffic and error rates have returned to normal levels following the fix. Graph loading and the graph editor are fully operational. This incident is now resolved — thank you for your patience.

A fix has been applied and graph loading and the graph editor are operating normally again. We are monitoring the service closely to confirm the issue is fully resolved.

We are investigating elevated 5XX errors affecting graph loading. Customers may be unable to load graphs or open the graph editor. Other platform functionality, including calls and conversations, is unaffected. Our team is actively investigating and we will share an update as soon as we know more.

The incident has been resolved. Dashboards are now fully operational and displaying data correctly for all companies. The root cause was identified as an issue with the materialized database views refresh process, which has been addressed. We apologize for any inconvenience caused during this time.

We can confirm that the incident is isolated to the Platform API and dashboard loading. The following services are fully operational and unaffected:

• Conversational Engine
• Inbound & Outbound Calls
• WhatsApp

Our team continues to work on resolving the materialized database views refresh issue. Next update to follow.

We are currently experiencing an incident affecting the Platform API. Dashboards are unable to load for users.

The incident began at 11:45 AM Paris time (09:45 UTC). We have identified the root cause as an issue with the materialized database views refresh process, manifesting as:

• A QueuePool connection limit breach (size 50, overflow 0 reached)
• The mv_daily_call_outcom_counts materialized view not being populated

Our team is actively working on a resolution. We will provide further updates as the situation develops.

This incident is now resolved. Our team, working alongside Activepieces support, identified the root cause affecting newly published graphs. A fix was developed, validated in pre-production, deployed to production, and re-tested to confirm the issue is fully resolved. Affected workflows should now be functioning normally. Thank you for your patience.

We have identified that a new version of ActivePieces introduced this issue. Custom action nodes and pre/post call flows may break when a bundle is published. We are actively investigating solutions and will share further updates as soon as possible.

We have identified additional impact: custom action nodes as well as pre and post call flows may break when a bundle is created. We are still actively investigating the root cause and will provide further updates as our investigation progresses.

We are currently investigating an issue affecting a subset of users who are unable to update action nodes on the platform. This does not impact overall platform availability and no downtime is occurring. Our team is actively looking into the root cause.