PROJECT MANAGEMENT

Escalate Long-Blocked Linear Issues to PagerDuty and Slack

Twice a day, scans Linear for issues that have been blocked longer than a threshold and escalates each one.

CategoryProject Management
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerTwice-daily schedule fires
  • ActionQuery blocked issues in active cycle from LinearLinearLinear
  • LogicFilter to issues blocked past aging threshold
  • LogicBranch by issue priority
  • ActionOpen PagerDuty incident for urgent blockersPagerDutyPagerDuty
  • OutputNudge assignee in Slack with blocker ageSlack

What it does

Catches sprint work that has quietly gone stuck. It finds Linear issues sitting in a blocked state past your aging threshold, then escalates based on priority so a blocked launch-critical issue gets real attention instead of dying in a backlog.

When to use it

When blocked issues routinely slip through standup and surface only at sprint review. Run it on a schedule so blockers get surfaced within hours, not days. Ideal for teams with on-call ownership who want urgent blockers to page someone.

How it works

  1. 1A schedule runs the check twice daily.
  2. 2Query Linear for issues currently in a blocked state within the active cycle.
  3. 3Filter to issues blocked longer than the configured aging threshold.
  4. 4Branch on priority: urgent or high blockers open a PagerDuty incident; the rest get a Slack nudge.
  5. 5Post a per-issue Slack message tagging the assignee with the blocker age and link.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LinearIssues, projects, cycles, triage.
  2. 2
    Connect PagerDutyIncidents, on-call, escalations.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.