Why does the second DB entry (and all the next ones) appear in DB for the same entity?

  • The second DB record (and, possibly, the next ones) for the affected entity means there have been Content Staging updates scheduled using the Magento_Staging module, which makes an additional record for an entity in the respective tables.

A problem would only occur if the records have the same values for the created_in or updated_in columns.

Solution

This is the expected behavior and will only lead to issues if there are discrepancies between the rows.

Previous pageTroubleshooting overview
Next pageChecking slow queries and processes MySQL

Commerce


Put the Customer at the Center and Build Relationships That Last a Lifetime

Online | Strategy Keynote | General Audience

First impressions last a lifetime. Great first impressions feel personal, connected, and relevant right from the start. From the first...

Wed, Mar 19, 2:30 PM PDT (9:30 PM UTC)

Register

B2B Reimagined: Transforming Go-to-Market Strategies for Profitable Growth

Online | Strategy Keynote | General Audience

B2B brands are facing a digital revolution. Buyers expect hyper-relevant content and self-service, while internally AI is transforming...

Wed, Mar 19, 1:00 PM PDT (8:00 PM UTC)

Register

Connect with Experience League at Summit!

Get front-row access to top sessions, hands-on activities, and networking—wherever you are!

Learn more