> For the complete documentation index, see [llms.txt](https://www.degenbot.wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.degenbot.wiki/understanding-alerts/outcomes-and-expiry.md).

# Outcomes and expiry

Understand what happened to an alert and why an unresolved result is not a win or a loss by assumption.

An alert's lifecycle starts with an observation and ends according to a defined evaluation rule. The exact status labels can differ by release; the concepts below explain what to look for.

| Concept                     | What it means                                                         |
| --------------------------- | --------------------------------------------------------------------- |
| Issued                      | The observation was recorded or sent.                                 |
| Open or pending             | Its outcome has not yet been finalised.                               |
| Successful                  | It met the method's defined success condition.                        |
| Unsuccessful or invalidated | It met the method's failure condition.                                |
| Expired or timed out        | Its evaluation window ended. How this is scored must be stated.       |
| Unresolved                  | There is not enough information yet to assign an outcome.             |
| Void or excluded            | It was removed from a particular calculation for a documented reason. |
| Corrected                   | A previous record was amended; the reason matters.                    |

These are explanations, not a claim that every label exists in the current interface.

### The rule matters more than the label

A favourable price movement is not automatically a successful alert. The method may require a level to be reached before an invalidation, within a fixed window, or after a defined reference time.

Likewise, an expiry is not automatically a loss, a neutral outcome, or an excluded result. Read how the active method counts it. If the rule is unavailable, the percentage is not fully interpretable.

### When both levels appear in one candle

Suppose a candle's high and low reach both a target and a stop. That candle alone may not reveal which happened first. A trustworthy evaluation needs a declared handling rule or sufficiently detailed data; it must not simply choose the favourable order.

This guide does not claim that Degen uses a particular tie-breaking rule. It is a release-verification item.

### Missing updates

No outcome message can mean the observation remains open, data is unavailable, delivery failed, or the report has not updated. It does not by itself prove that the alert won or lost.

Match follow-up messages using an alert identifier when present, or the symbol, stream, timestamp, and version. Report mismatches with both the original and the follow-up.

### Do not rewrite the past

Reading an old alert at today's price does not create a new alert. Changing a strategy or resolver version should not silently change the meaning of an older result. Review corrections and method versions before comparing totals.

Continue to **Performance and methodology → Use /performance**.