How to approach it
Compare canonicals in source and rendered HTML with redirects, sitemap entries and navigation links. Fix disagreements by making each component reference the preferred accessible URL.
Sort the issue into cases such as duplicates, temporary alternates, retired routes and competing content. A canonical link between pages with different inventory or intent can make the intended landing page ambiguous. Compare both text and catalogue composition, then review which version the menu, breadcrumbs and feed actually promote.
Worked example
A menu links to a collection-filter URL while the sitemap and canonical use a clean collection. Point the menu to the clean URL if it serves the same landing-page purpose.
How to verify the change
Test one template at a time. Inspect raw HTML and the rendered page, verify status on the target and compare what Search Console reports after recrawl. If a plugin emits a second canonical, fix the output at the template or plugin level and recheck a product, category and paginated view.
If the sitemap itself includes both variations, fixing the canonical tag is only one part of the work. Trace where sitemap entries originate and correct the publishing rule so the conflict does not return on the next release.