> 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/one-minute-long-short.md).

# 1m LONG+SHORT

Understand the short-term directional stream without confusing its timeframe with its outcome window.

**1m LONG+SHORT** is one of Degen's reported alert streams. It distinguishes upward and downward scenarios in a short-term market context.

The label `1m` must not be treated as a promise that an alert lasts one minute, resolves within one minute, or arrives every minute. The active release's message and method definition determine the actual horizon.

### How to read it

First check LONG versus SHORT, then the symbol, observation time, reference level, and any invalidation or expiry. Read whether the message describes an emerging condition or a follow-up to a condition already seen.

Short-term messages are especially sensitive to the gap between the observation and when you read it. A level that was relevant at the message timestamp may no longer describe the market in front of you.

### What not to assume

A one-minute chart interval does not mean the bot scans every market on exactly that schedule. It does not reveal the required move size, target/stop distance, cooldown, or outcome rule. Those details cannot be reconstructed from the stream name.

A LONG and a SHORT alert on the same symbol are not automatically duplicate mistakes. Compare their times, versions, and conditions. If they appear to describe the same moment with incompatible information, report both messages instead of guessing which one to follow.

### Reviewing a result

Match the result to the original alert and the same stream version. Check whether the original scenario reached the stated success condition within the defined window, or whether it was invalidated, expired, or left unresolved.

Do not compare this stream's accuracy directly with another stream until you have checked the outcome definitions and evaluation periods.

**Observe the sequence, not just the direction:** the time the condition was recorded, the time it reached Telegram, and what happened afterward each matter.

See **Outcomes and expiry** for the difference between a favourable move and a formally resolved alert. The exact thresholds and resolution policy remain a release-verification item for this draft.