See why two queued proposals conflict and how executing one affects the other before signing a replacement.

Two pending Safe transactions with the same Safe nonce are alternatives, not a sequence. Only one can execute; the successful transaction consumes that nonce and invalidates the competing proposal. This is how Safe's nonce explanation describes the conflict.
Check the nonce on both proposals
Open each transaction in the Safe queue on the same network and compare its nonce, destination, value, and data. A nonce is an on-chain sequence number for the Safe account. Do not confuse it with the separate nonce of the wallet that pays to execute a transaction. If the nonces differ, investigate a different queue or execution issue; see the approved but not executed guide.
Which conflicting proposal should you execute?
Review both full transactions with every signer who must approve. If you want the replacement, collect the threshold of signatures for that proposal and execute it. Once it is confirmed on-chain, the other proposal's nonce is used and that proposal cannot execute as written. A signature alone does not consume the nonce.
Is deleting a queued transaction the same as cancelling it?
No. Safe's reject and delete guide says deleting a queue entry is an off-chain action; someone who copied a sufficiently signed transaction may still be able to execute it. For an on-chain cancellation, Safe proposes a cancellation transaction with the same nonce, collects the required confirmations, and executes it. This consumes the nonce and entails a network fee. Confirm the intended nonce and transaction details before signing. A misleading link or fake support agent cannot safely “clear” the queue for you.
Official sources
Product interfaces and recovery policies can change. Confirm the current steps before acting.