...
The following is a sample notification sent out to the default case submitter email ID with the list of transactions as an attachment that were failed to create E-Verify case.
...
Transactions for which the E-Verify case could not be created are listed in the attached error report file. The case submission failure count given in the email will be in sync with the number of failed transactions present in the DHS_Error_Report.csv. If there are no failed transactions, then there will be no error file attached in the email.
Download the file and review the transactions that have failed to create the E-Verify case. Take action on these transactions to resolve the errors.
Using the invitation IDs mentioned in the error log, you can identify the invitations in My Tasks Console/Elasticsearch My Tasks category and take action to resolve the errors.
Once it is done, these transactions will again be considered for case creation during the next process cycle.
...
But for the transactions that are in "Out of Compliance" state, the E-Verify page will have the "Overdue Reason" populated from the Case Submitter details in DHS Client Setup.
| DHS Client Setup |
|---|
|
| Default Case Submitter Details |
|---|
|
Example: Out of Compliance transaction with Overdue Reason populated from DHS Client Setup Case Submitter Details.
...
In Elasticsearch, select E-Verify Console as the Category and search using an appropriate Keyword. In this case, "All" is used as the Keyword. Filter the search results for various DHS Status as needed.
As an example, here the search results are filtered for DHS Status = "Unconfirmed Data".
Click on the I-9 ID link to open the Unconfirmed Data page and continue with the verification process.
|
| Unconfirmed Data page |
|---|
|
How to check for EA Auto closed transactions?
...