[Critical Production Issue]: partial migration to V3 | ComposioHQ | Page 1

regal gull May 8, 2025, 2:09 PM

#

We've run into a critical issue in production that started a few hours ago, and we're hoping that this can be resolved ASAP.

Background:
Our app stores integration and connection data in our own database. Since we started using your services before V3, we've been referencing the V2 uuid for both integrationId and connectionId.

The Problem We're Seeing:

When our app fetches connection details, it seems the integrationId field is now returning a V3 nanoId instead of the V2 uuid our system expects. This is causing referential integrity failures in our database.
As a quick test, we tried updating an integrationId in our database to use the new V3 nanoId. However, when we then try to call client.connectedAccounts.initiate using this V3 nanoId, the API call is failing with a 500 status code.

SDK (JS):
Dev:(Composio-core: 0.5.38)
Prd:(Composio-core: 0.5.33)

This is causing significant disruption to our production services right now. Complains are starting to come, some new users are left without on-boarding.

We'd really appreciate any guidance or a quick fix to this.

cloud drumBOT May 8, 2025, 2:36 PM

#

Hi,

This is a bug that we identified and team is investigating this. We will keep you posted on this.
Are you doing this via SDK? If that's the case, it's expected to fail. In this case, please use v3 APIs directly.

Thanks!

regal gull May 8, 2025, 2:46 PM

#

Yes, we are using the SDK. Do we have to use the API in all cases then?

we have integrated and used SDK extensively in our backend.

We need definite answers for the following question.

Do we have to change all of the integrationId references to nanoId permanently?
What about connections? In the OAuth callback, we stil get the uuid as connectedAccountId

regal gull May 8, 2025, 4:07 PM

#

Hey what is the V3 API equivalent to client.connectedAccounts.initiate?

If it is the one referenced here: https://docs.composio.dev/api-reference/api-reference/v3/connected-accounts/create-a-new-connected-account, how to pass the id/slug of the toolkit? It is not mentioned in there

Introduction

jovial geyser May 8, 2025, 4:52 PM

#

regal gull Hey what is the V3 API equivalent to `client.connectedAccounts.initiate`? If it...

Yes, you're right — in the new API we don't support passing slug, you'll need to create an integration and pass that integration id. (integration is now called auth_config). Pls refer the v3 migration guide: https://docs.composio.dev/changelog/api-v-3-migration

Changelog & Updates

Tracking changes, deprecations, and migrations for Composio

regal gull May 8, 2025, 5:18 PM

#

Since the SDK is not ready yet, It is better for us to postpone the migration for now. Will you be able to fix the 1st issue mentioned in the original post?

cloud drumBOT May 8, 2025, 5:19 PM

#

Yes the first one is fixed, it’ll be live soon

regal gull May 8, 2025, 5:19 PM

#

Thank you. Looking forward.

regal gull May 9, 2025, 5:19 AM

#

It appears the issue is still present. We were unable to sync connections for a new user.
Do you have an ETA on when the fix for this will be deployed?

jovial geyser May 9, 2025, 8:11 AM

#

regal gull It appears the issue is still present. We were unable to sync connections for a ...

Fix will be live in next 3 hours

jovial geyser May 9, 2025, 9:46 AM

#

regal gull It appears the issue is still present. We were unable to sync connections for a ...

The fix is live!

regal gull May 9, 2025, 11:22 AM

#

Excellent, thank you! We've tested the fix, and it's working now.

We did notice one minor change to a key of a referential id in the connectedAccounts.get event payload: entityId has been renamed to clientUniqueUserId.

It's not a problem for us to adapt our code, we will change them to expect one or the other, but we thought you'd want to know.

#[Critical Production Issue]: partial migration to V3