ruvnet/ruflo · error · Error

message ID was reused with different content

Error message

message ID was reused with different content

What it means

The (issuer, messageId) identity key was already recorded by a prior send, but the new envelope's digest differs from the stored one — the same message ID is being reused with different content. Duplicate delivery is refused to preserve exactly-once identity semantics.

Source

Thrown at v3/@claude-flow/codex/src/harness/in-memory-inbox-reference.ts:98

    }
    try {
      parseCanonicalUnsigned(message.sequence, 'message sequence');
    } catch {
      throw new Error('message sequence must be a canonical unsigned decimal integer');
    }
    if (message.expiresAt !== undefined && !Number.isFinite(Date.parse(message.expiresAt))) {
      throw new Error('message expiresAt must be an ISO timestamp');
    }

    const envelopeDigest = sha256(canonicalJson(message));
    const prior = this.byIdentity.get(identity);
    if (prior) {
      if (prior.issuer !== message.issuer || prior.messageId !== message.messageId) {
        throw new Error('inbox identity hash collision');
      }
      if (prior.envelopeDigest !== envelopeDigest) {
        this.quarantine(message, 'message-id-content-conflict', receivedAt);
        throw new Error('message ID was reused with different content');
      }
      return { messageId: message.messageId, acceptedAt: prior.record.receivedAt, duplicate: true };
    }

    const record: InMemoryInboxRecord = {
      cursor: (this.nextCursor++).toString(),
      message: clone(message),
      receivedAt,
    };
    this.records.push(record);
    this.byIdentity.set(identity, {
      issuer: message.issuer,
      messageId: message.messageId,
      envelopeDigest,
      record,
    });
    return { messageId: message.messageId, acceptedAt: receivedAt, duplicate: false };
  }

View on GitHub (pinned to fa13ee4ad6)

Solutions

  1. Generate a fresh unique messageId for each new message instead of reusing ids.
  2. If id reuse is intentional for idempotent delivery, resend byte-identical content.
Defensive patterns

Strategy: validation

When it happens

Trigger: Thrown at v3/@claude-flow/codex/src/harness/in-memory-inbox-reference.ts:98 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of ruvnet/ruflo@fa13ee4ad6 (2026-08-18). Data as JSON: /api/errors/fa0c2d4fdc31af77. Report an issue: GitHub.