medusajs/medusa

Duplicate React key warning in `CustomerOrderSection` due to duplicate `"actions"` column IDs

Open

#15485 opened on May 24, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (22,539 stars) (2,090 forks)batch import
good first issuetype: bug

Description

Description

While navigating to the customer detail orders table, a React warning appears in the console:

Warning: Encountered two children with the same key, `0_actions`

After tracing the issue, it seems to originate from duplicate TanStack Table display column IDs.

useOrderTableColumns already defines a display column with:

columnHelper.display({
  id: "actions",
  cell: ({ row }) => {
    return <CountryCell country={country} />
  },
})

Then CustomerOrderSection appends another display column:

columnHelper.display({
  id: "actions",
  cell: ({ row }) => <CustomerOrderActions order={row.original} />,
})

This results in duplicate column IDs inside the same table, causing TanStack Table to generate duplicate internal keys such as:

0_actions

which triggers the React warning.

Expected behavior

Column IDs should be unique.

The CountryCell display column appears to semantically represent a country/shipping country column, so renaming its ID from:

id: "actions"

to something like:

id: "country"

would likely resolve the warning.

Environment

  • Admin dashboard
  • TanStack Table

Contributor guide

Tech stack
typescriptreact
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
ReactTanStack TableMedusa admin setup
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
Look at the file `useOrderTableColumns` which defines a display column with id 'actions' for a CountryCell. Also check `CustomerOrderSection` where another display column with the same id is appended. Rename the id in `useOrderTableColumns` from 'actions' to 'country' to eliminate the duplicate key warning. Ensure no other references to that column id break.