Skip to content

fix: preserve original booking scheduledFor when processing COPY migr…#1388

Open
mazzopardi2 wants to merge 4 commits intomasterfrom
bug-portal-timestamp
Open

fix: preserve original booking scheduledFor when processing COPY migr…#1388
mazzopardi2 wants to merge 4 commits intomasterfrom
bug-portal-timestamp

Conversation

@mazzopardi2
Copy link
Copy Markdown
Contributor

@mazzopardi2 mazzopardi2 commented Apr 2, 2026

Issue:

When processing a COPY record through the resolve migrations pipeline, the booking's scheduledFor and the capture session's startedAt/finishedAt timestamps are incorrectly overwritten with the COPY's values. COPY records reuse the original record's booking and capture session, so these fields should be preserved - but instead they get replaced with different values from the COPY.

Fix:

For COPY records, the existing booking's scheduledFor and the existing capture session's startedAt, finishedAt, startedByUserId, and finishedByUserId are now fetched and preserved rather than being overwritten. For ORIG (non-COPY) records, behaviour is unchanged.

Test plan:

[ x ] Migrate an ORIG recording and verify scheduledFor and capture session timestamps are set correctly from the archive name
[ x ] Migrate a COPY record for the same booking via the resolve migrations pipeline and verify scheduledFor and capture session timestamps remain unchanged from the original

@mazzopardi2 mazzopardi2 requested a review from a team as a code owner April 2, 2026 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant