[MS-1243] Controlling the matcher execution with the isMatcherRunning flag

[alexandr-simprints]

JIRA ticket
Will be released in: 2025.4.0

Root cause analysis (for bugfixes only)

First known affected version: 2025.4.0

When performing a 1:N identification with commcare around 15k records, SID restarts the identification process if the device screen locks during the operation. This causes the ongoing matching session to be lost and forces the user to restart the entire identification process.

Notable changes

isMatcherRunning is added to the MatchViewModel that prevents ViewModel to restart the ongoing matcher

Testing guidance

• Start a 1:N identification with ~15,000 records.
• Allow the screen to lock automatically or lock it manually during the process.
• Unlock the screen and verify that matcher is still running

Additional work checklist

• Effect on other features and security has been considered
• Design document marked as "In development" (if applicable)
• External (Gitbook) and internal (Confluence) Documentation is up to date (or ticket created)
• Test cases in Testiny are up to date (or ticket created)
• Other teams notified about the changes (if applicable)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud