Error search
Last updated
Last updated
You can search for the errors occurred during the selected period in the IMQA WCrash error search page. You can search by rank, app version, tag, etc., and open the detailed page of the error in question quickly.
The IMQA WCrash error search page is composed of the following.
❶ Filter ❷ Error table
You can filter the errors displayed in the error table, using date, status, device, OS version, browser, and tag.
❶ Date Sets to “7 days” by default. Errors can be filtered by up to 30 days. You can change the maximum date by dragging the mouse over the bar.
❷ Status Sets to “All” by default. Errors can be filtered by the status set in the “Error details” page.
❸ Device Sets to “All” by default. Errors can be filtered by ‘Desktop’ or ‘Mobile’.
❹ OS version Sets to “All” by default. Errors can be filtered by four OS versions with most frequent errors, etc.
❺ Browser Sets to “All” by default. Errors can be filtered by four browsers with most frequent errors, etc.
❻ Tag
Sets to “All” by default. Errors can be filtered by tag after selecting it from the list of all tags set in the “Error details” by clicking Select. Select tag desired tag to add a filter condition. Click the [X] icon to delete the tag.
Errors can be viewed using the condition selected in the filter. The table shows cumulative count, error name, current status, and last occurrence date. Using this table, you can understand occurred errors quickly and open the “Detailed page by error”.
❶ Header(sort) By default, errors are aligned by Most recent. Other alignment types include Cumulative count, Status, Date.
❷ Error Errors are displayed using the condition selected in the filter. If you click on an error item, the “Error details” page will open.
Status: Displays the status set in the “Error details” page.
Count: Counts the occurrence of the error in question cumulatively.
Name: Displays the error type, custom error message.
Tags: Displays the tag set in the “Error details” page.
Date: Displays the date and time when the error in question occurred.
