DHQ and CSH Surveys: Null Survey Status for Active Verified Participants

[JoeArmani]

The DHQ and CSH surveys are set to "not started" during participant verification when the status changes from "not verified" to "verified." These become active 180 days and 270 days after verification, respectively.

The typical verification case is handled, but edge cases where status starts with a value other than "not verified" and is updated to "verified" don't appear to be handled.

Unhandled cases appear to include verifications via the verification corrections tool and API verifications that start with a status other than "not verified." This has resulted in null survey status variables for these two surveys among participants with non-standard paths to verification, making these two surveys inaccessible in the PWA.

Box doc with affected pts as of 12/17/2025:
https://app.box.com/s/ejvnhb27p6enskrn8shn16154mge4v18

Query terms:
Verification stauts = Verified
Withdrawn = No
Has refused future activities = No
Has refused future surveys = No
Is deceased = No

DHQ-specific term:
Verified on or after 12/01/2024

DHQ Query:

SELECT Connect_ID, d_821247024 AS Verification_Status, d_914594314 as Verification_Timestamp, d_692560814 AS DHQ_Survey_Status FROM `[Participants]`
WHERE d_821247024 = 197316935
AND d_914594314 >= "2024-12-01T00:00:00.000Z"
AND d_747006172 = 104430631
AND d_906417725 = 104430631
AND d_685002411.d_867203506 = 104430631
AND d_987563196 = 104430631
AND d_692560814 is NULL
LIMIT 1000

CSH Query:

SELECT Connect_ID, d_821247024 AS Verification_Status, d_914594314 as Verification_Timestamp, d_176068627 AS CSH_Survey_Status, FROM `[Participants]`
WHERE d_821247024 = 197316935
AND d_747006172 = 104430631
AND d_906417725 = 104430631
AND d_685002411.d_867203506 = 104430631
AND d_987563196 = 104430631
AND d_176068627 is NULL
LIMIT 1000

To resolve manually (until we've updated the verification API and verification corrections tool):
For each affected participant in Firestore, set survey status to "not started":
DHQ -- 692560814: 972455046
CSH -- 176068627: 972455046

[JoeArmani]

What we'll need to fix this:
All verification paths where verification status can go from [some non-verified status] -> verified, so we can handle any non-standard verification cases.

[robertsamm]

Hi @JoeArmani I have moved this item to the Jan Release, unless you think we need a separate github issue for the fix to the data corrections tool + API?