Conflicts not appearing in the Conflict Feed

Question

Conflicts not appearing in the Conflict Feed

João Pereira 0

Hello everyone!

I'm currently trying to understand how to generate conflicts in order to test some stored procedures I've developed to solve conflicts. Right now I'm not testing the stored procedures, I'm just trying to understand how can I generate conflicts. Well, I'm using the Java SDK, and when I perform multiple updates in two different regions, I can generate a couple of conflicts (I am printing the conflict feed in my code). The problem is that those conflicts don't appear in the conflict feed in the Azure Portal.

My question is if this is a bug from the portal or can some of my updates being upserting the conflicts?

Mahesh Kurva 3,575 Reputation points Microsoft External Staff

2025-04-07T02:13:53.62+00:00
Hi João Pereira,

Greetings!

The problem is that those conflicts don't appear in the conflict feed in the Azure Portal.

Conflicts only show up in the conflict feed if there’s an error in your designated stored procedure during the conflict resolution process.

If your stored procedure resolves the conflict successfully, the conflict is resolved, and it doesn't get logged in the conflict feed.

If there's a failure in your conflict resolution logic or if the system cannot resolve the conflict, then the conflict will appear in the feed for you to inspect and address manually.

For more information, please refer the document: https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/how-to-manage-conflicts?tabs=dotnetv2%2Capi-async%2Casync%2Cv4async#create-a-custom-conflict-resolution-policy-using-a-stored-procedure

I hope this information helps. Please do let us know if you have any further queries.
João Pereira 0 Reputation points

2025-04-07T10:33:05.48+00:00

Hello @Mahesh Kurva! Thank you for the reply.I though that if I don't have a stored procedure, the conflicts will be displayed in the conflict feed, in the Azure Portal. That's my problem, the conflicts don't appear in the portal but they appear when I iterate over the conflict feed on my code.
Mahesh Kurva 3,575 Reputation points Microsoft External Staff

2025-04-09T02:14:20.03+00:00
Hi João Pereira,

Apologies for causing the issue.

To troubleshoot further:

Check the conflict resolution policy configured for your Cosmos DB container. If it's set to LWW, conflicts might not appear in the portal.

Try using explicit INSERT or UPDATE operations instead of upserts to see if conflicts behave differently.

Continue using your code to iterate over the conflict feed, as it seems to provide more detailed insights than the portal. For more information, please refer the document: https://learn.microsoft.com/en-us/azure/cosmos-db/conflict-resolution-policies?source=recommendations

I hope this information helps. Please do let us know if you have any further queries.
Mahesh Kurva 3,575 Reputation points Microsoft External Staff

2025-04-10T02:29:52.8966667+00:00

Hi João Pereira,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Mahesh Kurva 3,575 Reputation points Microsoft External Staff

2025-04-11T02:01:30.1966667+00:00

Hi João Pereira,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
João Pereira 0 Reputation points

2025-04-11T12:01:34.6+00:00

I still have no resolution.

1 answer

Your answer

Mahesh Kurva 3,575 Reputation points Microsoft External Staff

2025-04-07T02:13:53.62+00:00

Hi João Pereira,

Greetings!

The problem is that those conflicts don't appear in the conflict feed in the Azure Portal.

Conflicts only show up in the conflict feed if there’s an error in your designated stored procedure during the conflict resolution process.

If your stored procedure resolves the conflict successfully, the conflict is resolved, and it doesn't get logged in the conflict feed.

If there's a failure in your conflict resolution logic or if the system cannot resolve the conflict, then the conflict will appear in the feed for you to inspect and address manually.

For more information, please refer the document: https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/how-to-manage-conflicts?tabs=dotnetv2%2Capi-async%2Casync%2Cv4async#create-a-custom-conflict-resolution-policy-using-a-stored-procedure

I hope this information helps. Please do let us know if you have any further queries.
João Pereira 0 Reputation points

2025-04-07T10:33:05.48+00:00

Hello @Mahesh Kurva! Thank you for the reply.I though that if I don't have a stored procedure, the conflicts will be displayed in the conflict feed, in the Azure Portal. That's my problem, the conflicts don't appear in the portal but they appear when I iterate over the conflict feed on my code.
Mahesh Kurva 3,575 Reputation points Microsoft External Staff

2025-04-09T02:14:20.03+00:00

Hi João Pereira,

Apologies for causing the issue.

To troubleshoot further:

Check the conflict resolution policy configured for your Cosmos DB container. If it's set to LWW, conflicts might not appear in the portal.

Try using explicit INSERT or UPDATE operations instead of upserts to see if conflicts behave differently.

Continue using your code to iterate over the conflict feed, as it seems to provide more detailed insights than the portal. For more information, please refer the document: https://learn.microsoft.com/en-us/azure/cosmos-db/conflict-resolution-policies?source=recommendations

I hope this information helps. Please do let us know if you have any further queries.
Mahesh Kurva 3,575 Reputation points Microsoft External Staff

2025-04-10T02:29:52.8966667+00:00

Hi João Pereira,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Mahesh Kurva 3,575 Reputation points Microsoft External Staff

2025-04-11T02:01:30.1966667+00:00

Hi João Pereira,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
João Pereira 0 Reputation points

2025-04-11T12:01:34.6+00:00

I still have no resolution.

Answer 1

Hi João Pereira,

To simulate a conflict in Azure Cosmos DB, you need to perform simultaneous updates to the same item in different regions. This kind of operation can result in a conflict, but whether that conflict is stored and visible in the conflict feed depends on your conflict resolution policy.

By default, Cosmos DB uses the Last Write Wins (LWW) strategy. With LWW, Cosmos automatically resolves the conflict by keeping the version of the item with the highest value for the configured conflict resolution path (usually a timestamp). This means the conflict is resolved automatically and not stored, so it won't appear in the conflict feed, either in the portal or via the SDK.

Conflicts that can occur include:

Insert conflicts – when the same ID is inserted at the same time in different regions.
Replace conflicts – when the same item is updated in multiple regions simultaneously.
Delete conflicts – when one region deletes an item while another updates it.

Since you're seeing conflicts in the SDK but not in the portal, it's likely because your updates are being resolved automatically using LWW. This is expected behavior and not a bug in the portal. If you want to see conflicts in the conflict feed, you need to configure your container with a custom conflict resolution policy that stores conflicts and optionally uses stored procedures to resolve them manually.

PratikLad 800 Reputation points Microsoft External Staff

2025-04-15T07:15:20.6266667+00:00

Hi João Pereira,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Narendra Pakkirigari 0 Reputation points Microsoft External Staff

2025-04-16T06:44:43+00:00

Hi João Pereira,

I hope you're doing well.

We wanted to follow up regarding your recent query. We haven’t heard back from you and were just checking in to see if you were able to find a resolution.

If you have identified a solution, we’d appreciate it if you could share it with the community, as it may be helpful to others facing similar issues. If you're still experiencing challenges, please feel free to provide additional details, and we’ll be happy to assist further.

Share via

Conflicts not appearing in the Conflict Feed

1 answer

Your answer