Use this guide to troubleshoot Runtime Errors, Error group details, Stack trace information, and investigations in Sortd-AI. Start by checking whether monitoring is enabled, then use the activity shown in Recent occurrences to determine whether Sortd-AI is receiving new Runtime Errors.
If the page says that no Runtime Errors have been received yet, send a new test error and check again. If the page shows a last received time but the list is empty, check the filters: clear State and Bug task filters before refreshing.
Automatic investigation requires more than repeated occurrences. Sortd-AI also checks that code-fix analysis is enabled, an analysed repo is connected, enough distinct sources have reported the Runtime Error, and the daily investigation limit has not been reached.
Open the Error group to see a reason such as:
The default investigation settings are 10 Occurrences, 2 Distinct sources, and a Daily cap of 5. You can change these values in Runtime error monitoring. The allowed ranges are 3–1000 for Occurrences, 1–100 for Distinct sources, and 0–50 for Daily cap.
Investigate now is available for an Open Error group. It is not available for an Error group that is already Investigating, Muted, or Resolved. If the action returns a message that the investigation is blocked, resolve the condition shown in the message—for example, enable code-fix analysis, connect an analysed repo, or wait for the daily cap to reset.
When monitoring is disabled, Sortd-AI does not record new Runtime Errors. Open Enable in settings, go to Runtime error monitoring, and enable Auto-investigate runtime errors. This setting is unavailable when code-fix analysis is disabled for the app.
Check the following:
After correcting the reporter, reproduce the problem once, return to Runtime Errors, and select Refresh. The page shows the last received time and the total number recorded when Sortd-AI has received Runtime Errors.
Sortd-AI combines recurring Runtime Errors into Error groups. The list therefore shows one row for a recurring error rather than one row for every occurrence. Open the matching Error group and review its occurrence count and Recent occurrences.
Sortd-AI records a sample of occurrences for inspection. An Error group shows the most recent sampled events, including time, release, route, environment, server, and whether the occurrence was handled. An empty Recent occurrences section does not necessarily mean that the Error group has no occurrences.
Sortd-AI groups Runtime Errors using a normalized error identity. Query strings and fragments are removed from route information, and messages are scrubbed before they are displayed. This can make several reports appear under one Error group when their changing details are not part of the underlying error.
Review Occurrences, Since last reset, First seen, Last seen, Environments, and Unhandled on the Error group detail page. Unhandled shows “Yes — crashed at least once” when the Error group has had an unhandled occurrence.
The Stack trace section displays the recorded sample. If no stack trace was included with the Runtime Error, it displays “No stack trace recorded.” Check that the reporter sends the complete stack information and that the correct app credentials are being used. Then generate a new Runtime Error and select Refresh.
Long stack traces and sensitive values may be shortened or scrubbed before they are displayed. If a new Stack trace is still missing, open the newest matching Error group and check Recent occurrences for the event details that were received.
An Error group can exist without a Bug task. Automatic investigation only creates a Bug task after the Error group passes the configured safety and noise checks. An Error group may also show a skip reason when an investigation has not been started.
For an Open Error group, select Investigate now to start an investigation manually. This bypasses only the occurrence and distinct-source checks; it does not bypass the requirement for monitoring and code-fix analysis, an analysed repo, or the daily investigation cap.
When a Bug task exists, select View bug task to open it. If you need to return to the list, select Back to errors.
An Error group can be Open, Investigating, Muted, or Resolved. New Runtime Errors can reopen a Resolved Error group when the problem occurs again. Muting or resolving an Error group changes its status, but does not change the status of a linked Bug task.
Contact Sortd-AI support when:
Include the app name, the Error group name, the approximate time of the Runtime Error, and screenshots of the relevant Stack trace, Recent occurrences, or status message. Do not include passwords, app credentials, access tokens, or sensitive customer information.