Retry Match

The retry_match() function is designed to manage scenarios where a record match requires a retry. It determines the current processing mode (batch or interactive), handles necessary logging, and resets the matches data structure to ensure the retry process begins afresh. This function maintains system stability and provides transparency through detailed operator logs.

Processing Workflow

Identify the Operator (User.getId())
- Determines whether the process is running in batch or interactive mode by retrieving the current user's ID.
Handle Batch Mode
- If no operator is detected, the function pauses the process and displays the current record message to avoid proceeding without resolution.
Handle Interactive Mode
- Resets the matches data structure to start a new match attempt.
- Logs the retry action, associating it with the current operator for accountability and tracking.

Functions Summary

Function Name	Purpose	Key Steps
`retry_match()`	Handles retrying a match by resetting data and logging the action.	Identifies the operator to determine batch or interactive mode. If in batch mode, the function pauses with a message. For interactive mode, the `matches` structure is reset, and the operator's action is logged.
`User.getId()`	Retrieves the current user's ID.	Checks the current user session and returns the operator ID if present. If no operator is detected, it indicates batch mode.
`Record.getMessage()`	Fetches the current record message.	Accesses the status or message associated with the current record to provide information for logging or pausing workflows.
`Record.wait()`	Pauses the process in batch mode to wait for resolution.	Displays the current record message and halts the workflow until the issue is resolved or user input is received.
`Record.log()`	Logs a message for debugging or tracking.	Formats the log message and appends it to the system log for traceability and transparency in the retry process.

Match Retry Functions

`retry_match`

Purpose: Handles the retry process for matching a record. Determines the mode of operation (batch or interactive) and prepares the system for a new match attempt by resetting the matches data structure and logging the operator's action.

void retry_match() {
    operator = User.getId();
    
    if (operator == null) {
        Record.wait(Record.getMessage());
    } else {
        matches = {};
        Record.log(operator + " is retrying match ");
    }
}

Key Steps:

Retrieve the Operator: Identifies the current user via User.getId(). If no operator is detected, the system identifies this as batch mode.
Handle Batch Mode: When running in batch mode (operator == null), the function pauses with the current record message, ensuring the process does not proceed until the issue is addressed.
Handle Interactive Mode: Resets the matches data structure to ensure a clean start for the match retry. Logs the operator's action to provide traceability.

Usage Instructions:

Use retry_match() when a match retry scenario arises.
Check system logs to confirm operator actions and status.
For batch mode, resolve any pending record messages before proceeding.

Examples and Notes:

Batch Mode Example:
If no operator is detected, the function pauses and displays a message such as "No matches found". The workflow will not resume until user input resolves the issue.
Interactive Mode Example:
When an operator (e.g., "User123") retries a match, the system logs the action as:
"User123 is retrying match"
Resetting Matches:
The reset of the matches data structure ensures the retry begins with a clean slate, eliminating potential conflicts from previous attempts.

Last modified: 13 January 2025