Not enough to go on
Low confidence
Insufficient signal to classify; requesting more information from the reporter.
What Nirna found
-
Ticket NRNA-9 arrived with limited identifying detail.source ↗
What this means
Inference: not enough evidence to attribute a cause without further information from the reporter.
Who’s affected
Accounts affected
0
isolated so far
First seen
Jul 23 · 23:34 UTC
Recommended fix
No action needed
Suggested replies
Copy-paste ready. Your engineer edits and sends.
Customer reply
Hi — thanks for the report. To investigate this we need a bit more information: the affected account ID, the user account or email involved, and an approximate time the issue started. With those we can pull the relevant telemetry and respond with a concrete next step.
Internal note
Needs-info: identifier resolution confidence 0.95. Sweep evidence was insufficient to call a verdict. Replied to the reporter asking for account/user identifiers and timing.
Why Nirna reached this conclusion
Verdict — Not enough to go on. We could only match this ticket to an account with 95% confidence — below the threshold to classify, so we'd rather ask than guess.
Confidence — Low. The checks barely cleared the bar. Treat this as a lead to follow, not an answer.
Who fixes it — No action needed. No fix yet — the evidence doesn't point at a cause to act on.
Who’s affected. Only the reporting account is affected in this window.
| Signal | Score |
|---|---|
| Account matched from ticket text | 0.95 |
| Recent deploy touched failing path | 0.00 |
| Account configuration mismatch | 0.00 |
| Code change in the failing path | 0.00 |
| Feature-flag rollout mismatch | 0.00 |
| Similar recent tickets | 0.00 |
| Different accounts affected | 0.00 |
Was this triage right?
Corrections apply the same day. A wrong-account correction with a domain hint updates the routing rules for the next ticket automatically.