You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
For the forward Reliable request execution we are getting expected response code as 202.Though we are getting expected response , inbound service logs shows the DuplicatePrimaryKeyError error.
We are using Azure cosmos DB for mongo api instead of Dynamo DB docker Image. Similar behavior seen when Dynamo DB docker image used instead of Azure cosmos DB instance.
To cross check, we executed this request with the help of shell script which are present at below link and found same issue.
Error:
E11000 duplicate key error collection: integration-adaptors.mhs_state. Failed _id or unique index constraint., full error: {'index': 0, 'code': 11000, 'errmsg': 'E11000 duplicate key error collection: integration-adaptors.mhs_state. Failed _id or unique index constraint.'}
Description:
For the forward Reliable request execution we are getting expected response code as 202.Though we are getting expected response , inbound service logs shows the DuplicatePrimaryKeyError error.
We are using Azure cosmos DB for mongo api instead of Dynamo DB docker Image. Similar behavior seen when Dynamo DB docker image used instead of Azure cosmos DB instance.
To cross check, we executed this request with the help of shell script which are present at below link and found same issue.
Error:
E11000 duplicate key error collection: integration-adaptors.mhs_state. Failed _id or unique index constraint., full error: {'index': 0, 'code': 11000, 'errmsg': 'E11000 duplicate key error collection: integration-adaptors.mhs_state. Failed _id or unique index constraint.'}
Test data -
outbound_script.txt
inbound_script.txt
Priority - Medium
@michael-kainos
The text was updated successfully, but these errors were encountered: