PROJECT MANAGEMENT
Deadlock Trend Report from Postgres Dependency Snapshots
Snapshots the daily blocked-by graph into Postgres, detects active deadlocks, and emails leads a weekly report showing which cycles are new, which persist, and how long each has…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily + weekly schedule
- ActionFetch dependency graph and detect cycles in LinearLinear
- ActionSnapshot cycles and edges to PostgresPostgres
- LogicDiff against prior snapshots; classify and age each cycle
- OutputEmail leads the ranked weekly deadlock reportGmail
What it does
A one-off deadlock alert is easy to ignore; a cycle that has been live for three weeks is not. This workflow records the dependency graph to Postgres every day, then once a week compares snapshots to report which deadlocks are brand new, which are recurring, and the age of each, turning a moment-in-time check into a trend you can manage.
When to use it
Use it when leadership needs accountability on stale cross-team blockers, not just a notification. The persisted history lets you prove a cycle has lingered and prioritize accordingly.
How it works
- 1A daily schedule triggers the snapshot run.
- 2Fetch the current open dependency graph from Linear and detect active cycles.
- 3Write today's cycles and edges into a Postgres history table.
- 4On the weekly run, query Postgres to diff this week's cycles against prior snapshots.
- 5Classify each cycle as new, persistent, or resolved and compute its age.
- 6Email leads a ranked weekly report with the oldest unresolved deadlocks at the top.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect GmailRead, draft, send, label.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Project Management workflows
Scan Notion Meeting Notes for Action Items and Open ClickUp Dependency Tasks
On a schedule, parses recently edited Notion meeting-notes pages for action items that one team owes another and creates a ClickUp task for each, with due date and owner mapped.
Sprint-Retro Recap to Slack with Owner DMs
After a Zoom retro, posts a themed recap to the team Slack channel and direct-messages each owner the specific action items they committed to during the call.
Escalate Overdue Cross-Team Dependencies to Owners and Stakeholders
Each morning checks Linear for dependency-labeled issues past their due date and nudges the owner in Slack, escalating to the requesting team's lead if it stays unresolved.
CEO-Authored Weekly Cross-Team Dependency Risk Briefing
Weekly, the CEO agent gathers all tracked dependencies across Linear and ClickUp, reasons about which handoffs threaten upcoming milestones.
Zoom Sprint-Retro Audio to Themed Linear Action Board
Transcribes a recorded Zoom sprint retrospective, clusters the discussion into themes, and creates assigned Linear issues for each action item with the spoken owner attached.
Log every dependency slip to a Notion register and email the affected leads
On any Asana dependency slip, appends a structured row to a Notion blocker register and emails the leads of the downstream teams so there is both an auditable record and a direct…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.