diff --git a/polkadot/node/network/collator-protocol/src/validator_side/claim_queue_state/basic.rs b/polkadot/node/network/collator-protocol/src/validator_side/claim_queue_state/basic.rs
index 1037e8e0427e8..47f3bf53f2a52 100644
--- a/polkadot/node/network/collator-protocol/src/validator_side/claim_queue_state/basic.rs
+++ b/polkadot/node/network/collator-protocol/src/validator_side/claim_queue_state/basic.rs
@@ -173,11 +173,12 @@ impl ClaimQueueState {
 				Some(future_block) => {
 					let future_claim = future_block.claim.as_ref();
 					if future_claim != Some(expected_claim) {
-						gum::warn!(
+						gum::debug!(
 							target: LOG_TARGET,
 							?future_claim,
 							?expected_claim,
-							"Inconsistency while adding a leaf to the `ClaimQueueState`."
+							leaf=?hash,
+							"Claim queue has changed. Expected on group rotations."
 						);
 
 						// There is an inconsistency. Update our view with the one from the claim
diff --git a/prdoc/pr_11417.prdoc b/prdoc/pr_11417.prdoc
new file mode 100644
index 0000000000000..b0d7698e64f4e
--- /dev/null
+++ b/prdoc/pr_11417.prdoc
@@ -0,0 +1,14 @@
+title: Decrease the log level for claim queue inconsistency in `ClaimQueueState`
+doc:
+- audience: Node Dev
+  description: |-
+    Decrease the log level of "Inconsistency while adding a leaf to the `ClaimQueueState`..." log
+    message from WARN to DEBUG.
+
+    On group rotations the backing groups are assigned to different cores. In this case we start
+    fetching the claim queue for the newly assigned core and the future assignments in
+    `ClaimQueueState` are no longer valid so overwriting them is the right
+    thing to do.
+crates:
+- name: polkadot-collator-protocol
+  bump: patch