PROJECT MANAGEMENT

Real-Time Cycle Guard on New Blocked-By Links

Triggers the instant a blocked-by link is added in Linear, checks whether that single new edge closes a circular dependency.

CategoryProject Management
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerLinear webhook: blocked-by link addedLinearLinear
  • ActionFetch surrounding dependency graph from LinearLinearLinear
  • LogicReachability check: does new edge close a loop?
  • LogicBranch: cycle would be created?
  • OutputDM the link author in Slack to undo itSlack

What it does

Instead of catching deadlocks after the fact, this workflow prevents them at creation time. The moment someone adds a blocked-by relationship in Linear, it tests whether that one new edge completes a cycle, and if it does, it alerts the author right away so the bad link never settles into the backlog.

When to use it

Use it when you want a guardrail rather than a nightly audit. Best for fast-moving teams where catching the deadlock seconds after it is created saves days of confusion.

How it works

  1. 1A Linear webhook fires on a new or updated issue-relation event.
  2. 2Fetch the current dependency graph context around the two linked issues.
  3. 3Run a targeted reachability check: does the target already reach back to the source?
  4. 4Branch: if the new edge closes a loop, continue; otherwise exit silently.
  5. 5Look up the actor who created the link.
  6. 6Send that person a direct Slack warning naming the cycle and the link to remove.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LinearIssues, projects, cycles, triage.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.