Duplicate w3id envelope ID exists on two different eVaults with different bodies

[plansombl]

Description

During a group chat audit, a case was discovered where the same envelope ID (w3id) b8c99d41-84e7-593c-9ded-a4e4e5468681 exists on two different eVaults and holds two different bodies. This is a data integrity violation — envelope IDs should be globally unique across all eVaults.

How this duplication occurred needs to be investigated and resolved.

Steps to Reproduce

1. Look up envelope ID b8c99d41-84e7-593c-9ded-a4e4e5468681 across all eVaults.
2. Observe the same w3id is present on two separate eVaults.
3. Compare the bodies — they differ between the two eVaults.

Expected Behavior

Each w3id (envelope ID) should be globally unique across all eVaults. No two eVaults should share the same envelope ID, and an ID should only ever map to a single, consistent body.

Supporting Media

Desktop

• Device: N/A (backend/data issue)
• OS: N/A
• Browser: N/A
• Version: N/A

Additional Context

This issue was reported externally via WhatsApp message and includes an attached Word document ("Duplication of w3id case.docx") with a detailed description of the case. Please refer to that document for further details.

[talhaensomble96]

@coodos , here's the document which is attached on whatsap group

Duplication of w3id case.docx