Skip to content

Comments

Set amlListReactivatedDate for users who re-verified in 2026#3101

Merged
TaprootFreak merged 1 commit intodevelopfrom
fix/set-aml-reactivated-date
Jan 31, 2026
Merged

Set amlListReactivatedDate for users who re-verified in 2026#3101
TaprootFreak merged 1 commit intodevelopfrom
fix/set-aml-reactivated-date

Conversation

@TaprootFreak
Copy link
Collaborator

Summary

Sets amlListReactivatedDate for 3 users who properly re-verified in 2026 but the field was not set (bug fix).

Background

These users have:

  • amlListExpiredDate = 2023-12-31 (AML expired)
  • amlListReactivatedDate = NULL (bug - should be set)
  • DfxApproval completed in 2026
  • Ident completed in 2026

They are legitimately reactivated but amlListReactivatedDate was never set.

Affected Users

userDataId Ident Date DfxApproval Date → amlListReactivatedDate
1787 2026-01-20 2026-01-20 2026-01-20
3864 2026-01-28 2026-01-28 2026-01-28
9087 2026-01-19 2026-01-19 2026-01-19

Changes

  • migration/1769500000000-SetAmlReactivatedDate.js: Sets amlListReactivatedDate to DfxApproval date

Test plan

  • Verify query returns 3 users
  • Run migration on staging
  • Verify amlListReactivatedDate is set for all 3 users

These 3 users (1787, 3864, 9087) have properly re-verified with both
Ident and DfxApproval in 2026, but amlListReactivatedDate was not set.

This migration sets amlListReactivatedDate to their DfxApproval date.
@TaprootFreak TaprootFreak marked this pull request as ready for review January 31, 2026 20:38
@TaprootFreak TaprootFreak merged commit 9d687e9 into develop Jan 31, 2026
7 checks passed
@TaprootFreak TaprootFreak deleted the fix/set-aml-reactivated-date branch January 31, 2026 20:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant