What happened
What this says
Current to 11 Oct 26Sunita Bains reported duplicate order records from an import run on 10 Jun 2026, with each order appearing twice and corrupting reporting. Bethan Lister identified the import loaded the same batch twice. Solved by 17 Jun 2026.
Problem: An import running on 10 Jun 2026 loaded duplicate order records, with each order appearing twice in the system. This corrupted counts and reporting accuracy.
Handling: Bethan Lister identified the duplicates in the orders table and confirmed the import had run twice on the same batch. He escalated to the platform team to determine whether the issue was on BB-Demo's side or the connector. The ticket was solved by 17 Jun 2026, seven days after creation.
Watch: A duplicate import is a serious data integrity issue. Follow up on platform findings to identify whether this was a one-off customer error or a systemic BB-Demo process failure that could recur.
Details
Updated 9 Oct 26Trail
- internal_note · Bethan Lister 10 Jun 2026 11:24Duplicate records detected in orders table. Import ran twice on same batch. Checking if connector issue or import process failure.
- created · Sunita Bains 10 Jun 2026 15:19We've found duplicate records from a recent import. Each order appears twice in the system, which is messing up our counts and reporting. The import ran on 10 Jun 2026. Can your team help identify the root cause and clean this up?
- public_reply · Bethan Lister 10 Jun 2026 16:13Thanks for reporting. I spotted the duplicates in your orders table earlier today. The import loaded those records twice on the same batch. I'm investigating whether this was an issue on our side or with the connector. Will have more detail soon and a plan to clean them up.
- status_change · 21 Jun 2026 23:59