Issue Task Resolved

#110586Record history rollback writes two unrelated correlation ids

Benni Mack 09/01/26, 19:26 updated 09/02/26, 07:00

Description

RecordHistoryRollback::performRollback() runs up to two DataHandler instances — one for the command map (undelete / delete), one for the data map(field values) — and passes no CorrelationId to either start() call.

Each instance therefore generates its own random correlation scope, so a single logical rollback ends up as two unrelated scopes in sys_history. The undelete half and the field-restore half of the same rollback cannot be recognised as one operation, and there is no way to tell later which entries a rollback produced.

Expected: create one CorrelationId in performRollback() and hand it to both DataHandler::start() calls.

Reviews 3

History 14

  1. Benni Mack commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-09-02T07:00:10+00:00" > 09/02/26, 07:00 </span>

    Applied in changeset commit:3e0703d7d0b1a9d4920ea8a760d53266a681427d.