Error Status

Status is an arbitrary label you can apply to groups of errors based on a property value. For example, when you want to work on an error, you can set the status Assigned to Jane to all the errors with that message. You do this with the “Set Status” action in any of the UI pages. You can filter the UI to show you errors with your assignment status values using the Filter Toolbar.

setting and filtering status

There are several default status values already defined in your TrackJS account, and you can add as many additional statuses as are valuable for your team.

Status is applied to Errors asynchronously, and it might take up to 60 seconds for all of the errors matching your request to be tagged. Setting the status will set the status on all future errors matching your request as well.

When To Use Status

Status has many different use cases:

  • setting the version the error will be resolved
  • setting who is responsible for an error
  • setting the priority or impact of an error
  • setting the root cause of an error

Most TrackJS users will use a combination of the above based on their team workflow. For example, errors could be categorized on impact into P1, P2, and P3 statuses. As developers work on errors, they change the status to Assigned to Jane when it looks important. Jane could then change the status to Fixed in 3.2.1 or User Extension based on her findings.

Special Status Behavior

Errors tagged Informational will be excluded from your page quality reports, such as the weekly summary email. This status indicates that this event is not impactful to your users, but you still want to know when it occurs. This could be something like an unexpected action or an important usage event.