3rd Party: Mixpanel connector syncs failing with "Unknown client failure."

Resolved: We’ve resolved the issue. We have observed that instance rates are returning to normal levels, and affected connectors are syncing successfully
Incident Summary Description: We identified an issue with the engage/campaigns endpoint, which started failing with a 404 error as the API was deprecated from the source side
Timeline: Incident Start time: 2025-05-19 07:17 PM UTC Incident End time: 2025-05-20 06:01 AM UTC
Root Cause: We were using the endpoint(engage/campaigns), which started giving a 404 response. As per the update from Mixpanel support, this api was deprecated, which started causing the failure
Resolution: We have implemented a fix to skip campaign endpoint from the sync to resolve the sync failure issue. We are in communication with Mixpanel support team and we will take appropriate next steps to re-enable the sync for this table. As campaign is a full sync endpoint so there won't be any data loss once we start syncing this table.

A fix has been implemented and we are monitoring the results.

A hotfix has been created and is being prepared for deployment. We will provide an update as soon as the changes are live.

We have found the Mixpanel API is returning endpoints as "Invalid".

We are working with Mixpanel support to resolve these errors.

Mixpanel connectors started receiving 404 errors on certain API calls.

We are investigating the reason for these errors.