Skip to main content
In Error Tracking, all Issues have a status that helps you categorize and prioritize problems.

Status types

All newly discovered Issues have an initial status of For Review. Flashduty automatically updates status based on specific conditions, and you can also manually adjust it.

Auto-resolve issues

Flashduty automatically marks inactive or resolved Issues as Resolved:
If the last reported version of an Issue is more than 14 days old and the error hasn’t reappeared in newer versions, the system will automatically resolve it.
If the version tag is not set, when an Issue has no new error reports in the past 14 days, the system will automatically resolve it.
Properly configuring your application’s version tag is crucial for accurately identifying resolved Issues.

Auto-reopen issues

Flashduty has Issue detection capability. When a resolved Issue reappears and meets the condition set by its resolve mode, the system automatically reopens it and marks it as For Review status, and adds a Regression label.

What is regression?

Regression refers to a previously fixed problem appearing again, most often an unexpected return after a code update. Flashduty’s regression detection automatically identifies these situations, reopening related Issues instead of creating duplicate Issues, thereby preserving the complete context and history of the problem.

Regression detection mechanism

When an error is grouped into a Resolved Issue, whether it counts as a regression depends on the Issue’s resolve mode (see Resolve mode):
  • Reopen in a new version (default): only a version the Issue has not seen before triggers detection
  • Reopen on recurrence: any recurrence triggers detection, including repeats in the same version
  • An error without a version tag triggers detection in both modes
  • An error that occurred before the Issue’s resolve time does not trigger detection (duplicate delivery, or an old error an SDK buffered offline and sent late)
Once regression is detected, Flashduty will:
1

Change Status

Automatically change the Issue status to For Review
2

Add Label

Add a Regression label to the Issue for quick identification

Associated version configuration

Regression detection considers the service version information when the error occurred. With Reopen in a new version (default), detection is triggered only in a version the Issue has not seen before, after it was marked Resolved. With Reopen on recurrence, versions are not compared, so a recurrence in the same version also triggers detection.
Without a version tag, a resolved Issue that gets new errors is still marked “Regression”. However, the system can’t tell whether the errors came from a new version.

Resolve mode

Resolved is one status, but it comes in two resolve modes that differ in what should happen when the error comes back. They are not options next to Resolved but submenu items under it: the status dropdown has 4 items in all, and hovering Resolved expands two children, both of which set the Issue to resolved:
  • You can switch between the two at any time in the status dropdown. Switching only the mode does not change the Issue’s statistics or alert state.
  • New Issues default to Reopen in a new version, and so do Issues the system resolves automatically.
  • An error without a version tag reopens the Issue in both modes, because without version information old and fixed code cannot be told apart.
  • On reopening, the Issue goes to For Review, is marked as a regression, and records when and in which version it regressed. The status label in the list is narrow, so both modes show as Resolved; the details panel adds a “Reopen in a new version” note next to it.

Manually update status

You can manually update Issue status anywhere Issues are displayed, including the Issue list or details panel.
Manually Update Status

Manually Update Issue Status

Click the current status and select the new status from the dropdown menu. The dropdown has 4 items: For Review, Reviewed, Resolved (a submenu with Reopen on recurrence and Reopen in a new version), and Ignored. Each submenu item shows its reopen behavior; see Resolve mode.

Best practices

  • Continuous Monitoring: Regularly check Issues in For Review status to ensure new issues and regressions are handled promptly
  • Version Management: Always configure the correct version tag for your application so the system can accurately identify resolved issues

Next steps

View Errors

Learn how to view and analyze error details