Bug: Flagsmith returning 502 on /identities API

[vivonk]

Describe the bug
We have integrated the /identities API and we are trying to call it with the following payload but there seems some issue with this data -
Here when identifier is 68385f9726ad05c8e551a8d5be5cd8213f1e733346a9eb00e86f83df94639555, API returns 502 but when it's any other test identifier it works.
Also, I tried to replicate it with a different env key, there we don't see 502. This is only happening with the env key that we are using.

-> Request

curl --location 'https://edge.api.flagsmith.com/api/v1/identities' \
--header 'X-Environment-Key: <key>' \
--header 'Content-Type: application/json' \
--data '{
    "identifier": "68385f9726ad05c8e551a8d5be5cd8213f1e733346a9eb00e86f83df94639555",
    "traits": [
        {
            "trait_key": "instanceId",
            "trait_value": "650c79f77ade126caf5852fa"
        },
        {
            "trait_key": "isTelemetryOn",
            "trait_value": false
        },
        {
            "trait_key": "tenantId",
            "trait_value": "650c79fa7ade126caf585309"
        },
        {
            "trait_key": "type",
            "trait_value": "user"
        },
        {
            "trait_key": "email",
            "trait_value": "68385f9726ad05c8e551a8d5be5cd8213f1e733346a9eb00e86f83df94639555"
        },
        {
            "trait_key": "defaultTraitsUpdatedAt",
            "trait_value": 1695316874
        }
    ]
}'

To Reproduce

Steps to reproduce the behavior:

1. Make a request from the above-shared curl with the env key we are using, you will be able to see 502.
2. Now change the identifier to any test value and API will work (no 502)

Expected behavior
When we are sending the above payload with our env key, we expect it to return 200OK with the right response instead of a 502.

How are you running Flagsmith?

• SaaS at flagsmith.com

Additional context
Discord conversation link - https://discord.com/channels/517647859495993347/917719343930957846/1154656436220076084

[khvn26]

Hi! We've noticed an incorrect trait value is stored for a bunch of your identities under the "instanceId" key. Can you share how did you set those initially — e.g., via UI or using a specific API endpoint? Thanks!

[vivonk]

@khvn26 we use APIs only to store traits. Although what's the incorrect value that;s being stored? Is it any special char or something like that? Do you mind sharing it?
cc: @NilanshBansal

[khvn26]

we use APIs only to store traits

Would you mind sharing which specific endpoints you use?

Do you mind sharing it?

Sure. We have the numeric value 65096277351152464000000000000000000000000000000000000000000000000000000000000000000000000000000000 stored in our database. This is likely a result of an erroneous deserialisation, but I could not reproduce it with the instanceId value you've provided with the curl. Was there any other value you set earlier?

[vivonk]

@khvn26 thanks for sharing this. Let me check both things and get back to you by tomorrow morning IST time.

[dabeeeenster]

@vivonk can you describe exactly how you are setting the identities and traits? Are you using an SDK? Are you hitting our API directly?

[NilanshBansal]

@dabeeeenster @khvn26 we are using the Flagsmith Java SDK (v6.1.0). The method being invoked is getIdentityFlags(identifier, traits)

Ref: https://docs.flagsmith.com/clients/server-side#get-flags-for-an-identity
cc: @vivonk

[NilanshBansal]

we use APIs only to store traits

Would you mind sharing which specific endpoints you use?

Do you mind sharing it?

Sure. We have the numeric value 65096277351152464000000000000000000000000000000000000000000000000000000000000000000000000000000000 stored in our database. This is likely a result of an erroneous deserialisation, but I could not reproduce it with the instanceId value you've provided with the curl. Was there any other value you set earlier?

@khvn26 can you please share the unique flagsmith identifier that has this instanceId?
We only set instanceId which is mongo objectId and always has a 24-character limit.
cc: @vivonk

[NilanshBansal]

@khvn26 @dabeeeenster I believe this is some internal issue within flagsmith, with this unique identifier 68385f9726ad05c8e551a8d5be5cd8213f1e733346a9eb00e86f83df94639555
Making a request to the flagsmith api with this identifier and our env key returns 502 error, but if we change the identifier a bit, the request is successful.
Please check the below screenshots for reference.

cc: @vivonk

[dabeeeenster]

OK we're looking into this further.

[gagantrivedi]

we use APIs only to store traits

Would you mind sharing which specific endpoints you use?

Do you mind sharing it?

Sure. We have the numeric value 65096277351152464000000000000000000000000000000000000000000000000000000000000000000000000000000000 stored in our database. This is likely a result of an erroneous deserialisation, but I could not reproduce it with the instanceId value you've provided with the curl. Was there any other value you set earlier?

@khvn26 can you please share the unique flagsmith identifier that has this instanceId? We only set instanceId which is mongo objectId and always has a 24-character limit. cc: @vivonk

@NilanshBansal every identity that is giving 502 for you have this instanceId. e.g: 68385f9726ad05c8e551a8d5be5cd8213f1e733346a9eb00e86f83df94639555