Server Errors
When something fails on the server while people use ANTS Platform, the error is recorded in your organization and grouped on the Errors tab of the Support page. Admins review the groups and decide which ones to report to ANTS support.
Nothing is sent to ANTS until an Owner or Security & Compliance member raises a ticket from an error.
Open the Errors page
Select Support Tickets in the Support menu, then the Errors tab (/organization/<organizationId>/support/errors). Owners and Security & Compliance members also get a New server error notification in the bell that opens the error.
The error list
Each row is one error type in one server action of the app.
| Column | Meaning |
|---|---|
| Error | The action that failed, with the error type below it. |
| Period count | How many times it happened in the chosen Period. The column is named after the period, for example Last 7 days. |
| Total | How many times it happened since it was first seen. |
| Users | How many people hit it. |
| Last seen | When it last happened. |
| Status | New, Reported (with the ticket's Jira reference) or Ignored. |
- Period: Today (UTC), Last 7 days (default), Last 30 days or All time. Counts use UTC calendar days. Errors with no occurrence in the period are hidden.
- Status: New and reported (default), New, Reported or Ignored.
- Search by action or error type.
Counts can lag by about a minute.
Error details
Select a row to open the error:
- Occurrences, Users, First seen and Last seen.
- A chart of occurrences per day for the chosen period.
- Pages: the pages it happened on, with each page's share.
- Recent request references: the 5 latest request references, which ANTS support can match to the server logs.
Raise a ticket
Owners and Security & Compliance members can report an error to ANTS support:
- Open the error and select Raise ticket. The Feedback & Support panel opens with a bug report.
- Check the Title (it starts as "Server error in" followed by the action) and add Notes on what people were doing when it failed (optional).
- Review the Error report. It is added to the ticket under your notes and lists the error type, the action, the occurrences in total and for today, the last 7 days and the last 30 days, the users affected, first and last seen, the top pages and recent request references.
- Check your Contact details, add screenshots or trace files if they help, and select Send report.
The ticket is delivered like any other support ticket. The error then shows Reported with a link to the ticket. While the ticket is open and the error keeps happening, ANTS support gets the new count at most once an hour.
An error can have one open ticket at a time. Once its ticket is Resolved or Closed, removed by ANTS Support, or its delivery failed, the error shows New again and can be raised again.
Other members see "Ask an Owner or Security & Compliance Admin to raise this." instead of the buttons. With custom roles, raising and ignoring need Admin on the Support tickets module, and viewing the page needs Read & Write.
Ignore an error
Select Ignore on an error that is expected or harmless. It moves out of the default list and shows under the Ignored status. Select Stop ignoring to bring it back.
An ignored error comes back on its own (as New, or Reported if it has an open ticket) when it starts happening much more often: when its total count passes twice its count at the time it was ignored, plus 10.
Ignoring and un-ignoring are recorded in the audit log.
Notifications
When an error is seen for the first time in your organization, Owners and Security & Compliance members get a New server error notification in the bell, for up to 10 new errors per organization per UTC day.
What is recorded
- Only server errors are recorded. Validation, permission, not found, conflict and rate limit errors are not.
- For each occurrence: the error type, the failing action, the page, a request reference, the person and the time. Request and response content and the error message are never recorded.
- The page is recorded as the app's route pattern, for example
/project/[projectId]/traces/[traceId], never the real address, so no IDs, names or emails from the address are stored. Anything else is recorded as(unknown). - Each error keeps its total and daily counts, the people affected, up to 20 pages and the last 20 request references. A raised ticket carries only the number of people affected, not who they are.
- An error with no occurrence for 90 days and no open ticket is deleted.