Resolve Consistency Failure in Lighthouse Transaction Manager

What is causing this issue?

This issue is caused by variances between the amount displayed on the user screen and the transactions eligible to close according to the view options. Historically this has been caused by various issues, including: 

• Two or more different users logged in to Lighthouse Transaction Manager at the same time, attempting to close or modify the same group of transactions.
• Browser caching issues.
• Transaction issues that allow the transaction to be displayed in the list but not to close successfully.

How do I resolve this issue?

1. Log out of Lighthouse Transaction Manager, clear your browser's cache and cookies, then log back in and attempt the batch submittal again.
2. Attempt another web browser client (IE, Chrome, Firefox, Edge, Safari) and attempt the batch closure again. Keep a record of the browser(s) used.
   1.  

Internal:

• Have the customer attempt to connect to a different Lighthouse Transaction Manager server. Have the customer read the address from their web browser to determine what server cluster they are connected to. See, I need to Test a Limited Release for Lighthouse Transaction Manager (LTM). How do I test against the Limited Release servers?
• If the above steps have not allowed the customer to close their batch, there may be transaction issues in the batch. The customer can adjust their view settings to view by each transaction type (for example, refunds or voids) and close each card type one by one. This will narrow the issue down to the card type where the issue lies.
• Have the customer compare reports for the batch in Lighthouse Transaction Manager and their Point of Sale for the number of transactions and amount of the batch. Look for any transactions that are on one report but not the other.
• Look at the amount and count from the current transaction page in Lighthouse Transaction Manager. Compare that to the numbers displayed when they attempt batch close. Look for differences there. For example: if the current transactions show 4 transactions for $100.00, and the batch page shows 3 transactions for $80.00, you are looking for a transaction for $20 as the likely issue. Have the customer send the audit trail from the transaction to review for any abnormality.
• If the above steps have not revealed the issue and allowed the customer to close their batches, escalate to Technical Services for further review.