Skip to content

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

chore(ai-task): keep queue alert incidents open until the fix is deployed (#16457)

Hazem Adel4a82369c02db
diff --git a/.agents/skills/ai-task/SKILL.md b/.agents/skills/ai-task/SKILL.md
index 3b23cfa340a..75f186081df 100644
--- a/.agents/skills/ai-task/SKILL.md
+++ b/.agents/skills/ai-task/SKILL.md
@@ -285,6 +285,7 @@ The cards below are examples of that voice, not forms to fill in word for word.
- the Postgres replica for the row in question, read only.
- If the box isn't connected, say so and go on with code evidence alone.
- **Queue or job failure** (a "Queue Alerts" ticket, a BullMQ job, a failed run id, an `EngineError@...` or `RPC [...] handler threw` signature): run `/debug-failed-run` first. Use its Step 4 to find job ids for the signature across every queue, then Steps 1 to 3 on one of them. Its verdict (product bug, config or infra) drives the decision below. The signature is often a wrapper, so read `stacktrace[0]` before naming a cause.
+ - **Queue alerts are live incidents.** Each one opens a Better Stack incident (linked in the ticket) and a Linear ticket. When you pick one up, assign the ticket to yourself and remind the user to acknowledge the incident in Better Stack. It stays open until the fix is deployed, not just merged, or it fires again.
3. **Decide one of these** and write a short comment with the evidence (files, functions, PRs, numbers). Don't post the comment without the user's go-ahead.
- **Fixed already:** name the PR that fixed it, then move to Done.
- **Duplicate:** link the original. Set the duplicate relation first, then the status.